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

update PyYAML to fix CVE-2017-18342 #909

Merged
merged 5 commits into from
Apr 10, 2019
Merged

update PyYAML to fix CVE-2017-18342 #909

merged 5 commits into from
Apr 10, 2019

Conversation

tomkinsc
Copy link
Member

@tomkinsc tomkinsc commented Jan 4, 2019

CVE-2017-18342
Vulnerable versions: < 4.2b1
Patched version: 4.2b1
In PyYAML before 4.1, the yaml.load() API could execute arbitrary code. In other words, yaml.safe_load is not used.

CVE-2017-18342
Vulnerable versions: < 4.2b1
Patched version: 4.2b1
In PyYAML before 4.1, the yaml.load() API could execute arbitrary code. In other words, yaml.safe_load is not used.
@tomkinsc
Copy link
Member Author

tomkinsc commented Jan 4, 2019

So this is failing because the old version is still the current release.
pyyaml >3.13 is not yet available anywhere in non-beta form, and release of 4.2 was rolled back. See: yaml/pyyaml#193
A 4.x package for PyYaml is notably absent from anaconda/conda-forge which includes only finalized versions.

@dpark01 dpark01 closed this Jan 9, 2019
@tomkinsc tomkinsc reopened this Jan 10, 2019
@tomkinsc tomkinsc merged commit 89be1f3 into master Apr 10, 2019
@tomkinsc tomkinsc deleted the ct-update-pyyaml branch April 10, 2019 19:57
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.

3 participants