GHSA-2xwp-m7mq-7q3r CLI does not correctly implement strict mode
The AWS Encryption CLI fails to enforce strict mode, allowing decryption with unauthorized keys, bypassing intended security controls.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-2xwp-m7mq-7q3r?
GHSA-2xwp-m7mq-7q3r is a vulnerability in aws-encryption-sdk-cli, published on 28 Oct 2020.
Official description
In the affected versions, the AWS Encryption CLI operated in "discovery mode" even when "strict mode" was specified. Although decryption only succeeded if the user had permission to decrypt with at least one of the CMKs, decryption could be successful using a CMK that was not included in the user-defined set when the CLI was operating in "strict mode."
Affected users should upgrade to Encryption CLI v1.8.x or v2.1.x as soon as possible.
Which versions are affected by GHSA-2xwp-m7mq-7q3r?
4 open source packages ship an affected version, including aws-encryption-sdk-cli.
| Package | Affected | Fixed in |
|---|---|---|
aws-encryption-sdk-cli PyPI | All versions | 1.8.0 |
aws-encryption-sdk-cli PyPI | All versions | 1.8.0 |
aws-encryption-sdk-cli PyPI | From 2.0.0 | 2.1.0 |
aws-encryption-sdk-cli PyPI | From 2.0.0 | 2.1.0 |
How do I fix GHSA-2xwp-m7mq-7q3r?
Upgrade aws-encryption-sdk-cli to a fixed version for your release line: 1.8.0 or 2.1.0.
Is GHSA-2xwp-m7mq-7q3r being exploited?
There is no known exploitation of GHSA-2xwp-m7mq-7q3r in the wild and no public exploit code.