You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @tooptoop4 thanks for reaching out. I brought this up for discussion with the team, and they wanted me to highlight that the AWS CLI should not be affected by this CVE as it does not use the cryptography package for SSH certificates. There is a dependabot PR (#8030) raising the version ceiling for cryptography and we recommend tracking that for updates going forward. The team is currently blocked on merging that PR pending further review.
Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
Describe the bug
pip3 install https://github.com/aws/aws-cli/archive/refs/tags/2.13.6.tar.gz
Installed Resource
cryptography 40.0.1
Fixed Version
41.0.2
Expected Behavior
high cve gone with new cryptography
Current Behavior
high cve
Reproduction Steps
install latest v2
Possible Solution
No response
Additional Information/Context
No response
CLI version used
2.13.6
Environment details (OS name and version, etc.)
unix
The text was updated successfully, but these errors were encountered: