CVE-2020-8912
A vulnerability in the in-band key negotiation exists in the AWS S3 Crypto SDK for GoLang versions prior to V2.
Does this matter?
Lower severity and a low EPSS score (0.23%). Track it; it rarely justifies an emergency change on its own.
Description
A vulnerability in the in-band key negotiation exists in the AWS S3 Crypto SDK for GoLang versions prior to V2. An attacker with write access to the targeted bucket can change the encryption algorithm of an object in the bucket, which can then allow them to change AES-GCM to AES-CTR. Using this in combination with a decryption oracle can reveal the authentication key used by AES-GCM as decrypting the GMAC tag leaves the authentication key recoverable as an algebraic equation. It is recommended to update your SDK to V2 or later, and re-encrypt your files.
- CVSS 3.1
- 2.5 LOWCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
- EPSS
- 0.23% probability · 14th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-327
- Affected
- amazon/aws s3 crypto sdk
- Source
- cve-coordination@google.com
References
- https://aws.amazon.com/blogs/developer/updates-to-the-amazon-s3-encryption-client/?s=09Vendor Advisory
- https://github.com/google/security-research/security/advisories/GHSA-7f33-f4f5-xwgwExploit, Third Party Advisory
- https://aws.amazon.com/blogs/developer/updates-to-the-amazon-s3-encryption-client/?s=09Vendor Advisory
- https://github.com/google/security-research/security/advisories/GHSA-7f33-f4f5-xwgwExploit, Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.