Advisory

GHSA-2xwp-m7mq-7q3r

Also known as: None

Summary

CLI does not correctly implement strict mode

Details

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.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2020-10-28 17:05 UTC
Modified
2024-12-02 05:37 UTC

Affected packages and fixes

aws-encryption-sdk-cli

PyPI · All systems

Affected

  • introduced 0, fixed 1.8.0 (ecosystem)

Fixed versions

1.8.0

Fix

  • Fixed version 1.8.0
    pip install --upgrade aws-encryption-sdk-cli==1.8.0

aws-encryption-sdk-cli

PyPI · All systems

Affected

  • introduced 2.0.0, fixed 2.1.0 (ecosystem)

Fixed versions

2.1.0

Fix

  • Fixed version 2.1.0
    pip install --upgrade aws-encryption-sdk-cli==2.1.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences