CVE-2020-8912: Use of a Broken or Risky Cryptographic Algorithm
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.
References
- aws.amazon.com/blogs/developer/updates-to-the-amazon-s3-encryption-client/?s=09
- bugzilla.redhat.com/show_bug.cgi?id=1869801
- github.com/advisories/GHSA-7f33-f4f5-xwgw
- github.com/aws/aws-sdk-go/commit/1e84382fa1c0086362b5a4b68e068d4f8518d40e
- github.com/aws/aws-sdk-go/commit/ae9b9fd92af132cfd8d879809d8611825ba135f4
- github.com/aws/aws-sdk-go/pull/3403
- github.com/google/security-research/security/advisories/GHSA-7f33-f4f5-xwgw
- github.com/sophieschmieg/exploits/tree/master/aws_s3_crypto_poc
- nvd.nist.gov/vuln/detail/CVE-2020-8912
Detect and mitigate CVE-2020-8912 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →