CVE-2020-8912GHSA-7F33-F4F5-XWGWGO-2022-0635
In-band key negotiation issue in AWS S3 Crypto SDK for GoLang
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.34.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Google LLC AWS S3 Crypto SDK for GoLang
From stable · through V1
- github.com/aws/aws-sdk-goGo
fixed in 1.34.0
- github.com/aws/aws-sdk-goGo
All versions