-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Please port to a newer version of PyYAML #4042
Comments
The PR for this is already approved and waiting for merge. It is taking quite some time though :) |
Thanks. I'll look into cherry-picking the patch for openSUSE later today then. |
@justnance neither of those issues are relevant to allowing a newer pyyaml, could you please reopen this and/or review the patch in #4015? |
The 'awscli' package has not yet revised its requirements in order to support an adequate version of the 'PyYAML' package; until such time, manual intervention is required when attempting to use this library or the CLI tool. To workaround this incompatibility, install a supported version: pip install PyYAML>3.10,<=3.13 Refs: https://nvd.nist.gov/vuln/detail/CVE-2017-18342 Refs: aws/aws-cli#4042 Refs: aws/aws-cli#4015
The 'awscli' package has not yet revised its requirements in order to support an adequate version of the 'PyYAML' package; until such time, manual intervention is required when attempting to use this library or the CLI tool. To workaround this incompatibility, install a supported version: pip install PyYAML>3.10,<=3.13 Refs: https://nvd.nist.gov/vuln/detail/CVE-2017-18342 Refs: aws/aws-cli#4042 Refs: aws/aws-cli#4015
The currently used PyYAML@3.13 contains a Arbitrary Code Execution issue. Check https://app.snyk.io/vuln/SNYK-PYTHON-PYYAML-42159 and https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-18342 for more information. (Just as reference for the duplicate issue I added here: #4193). |
UP, UP, UP. please!!! |
For 5.1 this is done, but now there's a 5.1.1 After the last snub in my previous PR I'm not really inclined to try and fix this one |
The version range has been updated, closing this out. |
The dependency on `PyYAML` causing issue has been removed: aws/aws-cli#4042 See #548 and aws/aws-cli#4042
The current upstream release of PyYAML is 5.1 while aws-cli still depends on PyYAML <= 3.13.
Would be nice if aws-cli could be ported to the latest version of PyYAML that version dependency could be raised to 5.1 or higher.
The text was updated successfully, but these errors were encountered: