Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use safe_load() instead of insecure load() #26

Merged
merged 1 commit into from Aug 20, 2019

Conversation

leopoldjuergen
Copy link
Contributor

Replace yaml.load() by yaml.safe_load(). In PyYAML before 5.1,
the yaml.load() API could execute arbitrary code
if used with untrusted data (CVE-2017-18342).

Signed-off-by: Juergen Leopold leopoldj@de.ibm.com

Replace yaml.load() by yaml.safe_load(). In PyYAML before 5.1,
the yaml.load() API could execute arbitrary code
if used with untrusted data (CVE-2017-18342).

Signed-off-by: Juergen Leopold <leopoldj@de.ibm.com>
@coveralls
Copy link

Coverage Status

Coverage remained the same at 72.124% when pulling 6ff498a on juergen/CVE_2017_18342 into 8e78cc6 on master.

@leopoldjuergen leopoldjuergen merged commit 2d924b0 into master Aug 20, 2019
@leopoldjuergen leopoldjuergen deleted the juergen/CVE_2017_18342 branch August 20, 2019 15:17
@andy-maier andy-maier added this to the 0.4.0 milestone Nov 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants