CLI does not correctly implement strict mode

published 2020-10-28 6y ago modified 2024-12-02 last yr.

cvss: —; not scored
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

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.

Patch / fix

fixed in 1 links 1

pypi aws-encryption-sdk-cli 1.8.0, 2.1.0

github.com/aws/aws-encryption-sdk-cli@7d21b80 commit

Is GHSA-2xwp-m7mq-7q3r in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem	package	affected	fixed in
pypi	aws-encryption-sdk-cli	<1.8.0 >=2.0.0, <2.1.0	1.8.0 2.1.0

Classification

Weakness

CWE-326 Inadequate Encryption Strength

References

Sources

GitHub Advisory GHSA-2xwp-m7mq-7q3r

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.