How severe is GHSA-2xwp-m7mq-7q3r?

No CVSS score has been assigned to GHSA-2xwp-m7mq-7q3r yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2xwp-m7mq-7q3r?

GHSA-2xwp-m7mq-7q3r affects the following packages: aws-encryption-sdk-cli (PyPI), aws-encryption-sdk-cli (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-2xwp-m7mq-7q3r?

Update aws-encryption-sdk-cli to 1.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2xwp-m7mq-7q3r is resolved across your whole dependency graph.

How do I detect GHSA-2xwp-m7mq-7q3r in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aws-encryption-sdk-cli, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2xwp-m7mq-7q3r if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-2xwp-m7mq-7q3r actively exploited in the wild?

No public exploit code has been indexed for GHSA-2xwp-m7mq-7q3r yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-2xwp-m7mq-7q3r published, and has it been updated?

GHSA-2xwp-m7mq-7q3r was published on October 28, 2020 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CLI does not correctly implement strict mode

Real-World Exposure

2 pkgs affected

🐍aws-encryption-sdk-cli🐍aws-encryption-sdk-cli

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`aws-encryption-sdk-cli`	all versions	1.8.0`pip install --upgrade 'aws-encryption-sdk-cli==1.8.0'`
🐍PyPI	`aws-encryption-sdk-cli`	≥ 2.0.0&&< 2.1.0	2.1.0`pip install --upgrade 'aws-encryption-sdk-cli==2.1.0'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aws-encryption-sdk-cli, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update aws-encryption-sdk-cli to 1.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2xwp-m7mq-7q3r is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-2xwp-m7mq-7q3r in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works