CVE-2020-8897 Details
Description
A weak robustness vulnerability exists in the AWS Encryption SDKs for Java, Python, C and Javalcript prior to versions 2.0.0. Due to the non-committing property of AES-GCM (and other AEAD ciphers such as AES-GCM-SIV or (X)ChaCha20Poly1305) used by the SDKs to encrypt messages, an attacker can craft a unique cyphertext which will decrypt to multiple different results, and becomes especially relevant in a multi-recipient setting. We recommend users update their SDK to 2.0.0 or later.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://aws.amazon.com/blogs/security/improved-client-side-encryption-explicit-keyids-and-key-commitment/ | CVE | Vendor Advisory |
| https://github.com/google/security-research/security/advisories/GHSA-wqgp-vphw-hphf | CVE | ExploitMitigationThird Party Advisory |
| https://aws.amazon.com/blogs/security/improved-client-side-encryption-explicit-keyids-and-key-commitment/ | [email protected] | Vendor Advisory |
| https://github.com/google/security-research/security/advisories/GHSA-wqgp-vphw-hphf | [email protected] | ExploitMitigationThird Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-327 | Use of a Broken or Risky Cryptographic Algorithm | [email protected] |
| CWE-310 | Cryptographic Issues | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| amazon aws encryption sdk | < 2.0.0 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Nov 21, 2024 | CVE Modified | CVE |
| May 14, 2024 | CVE Modified | [email protected] |
| Dec 2, 2020 | Initial Analysis | [email protected] |