CVE-2020-8897
Vulnerability Scoring
Attack Complexity Details
- Attack Complexity: HIGH IMPACT
- Attack Vector: NETWORK
- Privileges Required: Low Impact
- Scope: UNCHANGED
- User Interaction: REQUIRED
CIA Impact Definition
- Confidentiality:
- Integrity: HIGH IMPACT
- Availability:
CVE-2020-8897 Vulnerability Summary
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.
Access Complexity Graph for CVE-2020-8897
Impact Analysis for CVE-2020-8897
CVE-2020-8897: Detailed Information and External References
EPSS
0.00121
EPSS %
0.47486
References
0.00121
- https://aws.amazon.com/blogs/security/improved-client-side-encryption-explicit-keyids-and-key-commitment/
- https://github.com/google/security-research/security/advisories/GHSA-wqgp-vphw-hphf
- https://aws.amazon.com/blogs/security/improved-client-side-encryption-explicit-keyids-and-key-commitment/
- https://github.com/google/security-research/security/advisories/GHSA-wqgp-vphw-hphf
CWE
CWE-327
CAPEC
0.00121
- Encryption Brute Forcing: An attacker, armed with the cipher text and the encryption algorithm used, performs an exhaustive (brute force) search on the key space to determine the key that decrypts the cipher text to obtain the plaintext.
- Creating a Rogue Certification Authority Certificate: An adversary exploits a weakness resulting from using a hashing algorithm with weak collision resistance to generate certificate signing requests (CSR) that contain collision blocks in their "to be signed" parts. The adversary submits one CSR to be signed by a trusted certificate authority then uses the signed blob to make a second certificate appear signed by said certificate authority. Due to the hash collision, both certificates, though different, hash to the same value and so the signed blob works just as well in the second certificate. The net effect is that the adversary's second X.509 certificate, which the Certification Authority has never seen, is now signed and validated by that Certification Authority.
- Signature Spoof: An attacker generates a message or datablock that causes the recipient to believe that the message or datablock was generated and cryptographically signed by an authoritative or reputable source, misleading a victim or victim operating system into performing malicious actions.
- Signature Spoofing by Improper Validation: An adversary exploits a cryptographic weakness in the signature verification algorithm implementation to generate a valid signature without knowing the key.
- Cryptanalysis of Cellular Encryption: The use of cryptanalytic techniques to derive cryptographic keys or otherwise effectively defeat cellular encryption to reveal traffic content. Some cellular encryption algorithms such as A5/1 and A5/2 (specified for GSM use) are known to be vulnerable to such attacks and commercial tools are available to execute these attacks and decrypt mobile phone conversations in real-time. Newer encryption algorithms in use by UMTS and LTE are stronger and currently believed to be less vulnerable to these types of attacks. Note, however, that an attacker with a Cellular Rogue Base Station can force the use of weak cellular encryption even by newer mobile devices.
- Rooting SIM Cards: SIM cards are the de facto trust anchor of mobile devices worldwide. The cards protect the mobile identity of subscribers, associate devices with phone numbers, and increasingly store payment credentials, for example in NFC-enabled phones with mobile wallets. This attack leverages over-the-air (OTA) updates deployed via cryptographically-secured SMS messages to deliver executable code to the SIM. By cracking the DES key, an attacker can send properly signed binary SMS messages to a device, which are treated as Java applets and are executed on the SIM. These applets are allowed to send SMS, change voicemail numbers, and query the phone location, among many other predefined functions. These capabilities alone provide plenty of potential for abuse.
- Cryptanalysis: Cryptanalysis is a process of finding weaknesses in cryptographic algorithms and using these weaknesses to decipher the ciphertext without knowing the secret key (instance deduction). Sometimes the weakness is not in the cryptographic algorithm itself, but rather in how it is applied that makes cryptanalysis successful. An attacker may have other goals as well, such as: Total Break (finding the secret key), Global Deduction (finding a functionally equivalent algorithm for encryption and decryption that does not require knowledge of the secret key), Information Deduction (gaining some information about plaintexts or ciphertexts that was not previously known) and Distinguishing Algorithm (the attacker has the ability to distinguish the output of the encryption (ciphertext) from a random permutation of bits).
Vulnerable Configurations
-
cpe:2.3:a:amazon:aws_encryption_sdk:-:*:*:*:*:*:*:*
cpe:2.3:a:amazon:aws_encryption_sdk:-:*:*:*:*:*:*:*
-
cpe:2.3:a:amazon:aws_encryption_sdk:0.0.1:*:*:*:*:*:*:*
cpe:2.3:a:amazon:aws_encryption_sdk:0.0.1:*:*:*:*:*:*:*
-
cpe:2.3:a:amazon:aws_encryption_sdk:1.3.0:*:*:*:*:*:*:*
cpe:2.3:a:amazon:aws_encryption_sdk:1.3.0:*:*:*:*:*:*:*
-
cpe:2.3:a:amazon:aws_encryption_sdk:1.3.1:*:*:*:*:*:*:*
cpe:2.3:a:amazon:aws_encryption_sdk:1.3.1:*:*:*:*:*:*:*
-
cpe:2.3:a:amazon:aws_encryption_sdk:1.3.2:*:*:*:*:*:*:*
cpe:2.3:a:amazon:aws_encryption_sdk:1.3.2:*:*:*:*:*:*:*
-
cpe:2.3:a:amazon:aws_encryption_sdk:1.3.3:*:*:*:*:*:*:*
cpe:2.3:a:amazon:aws_encryption_sdk:1.3.3:*:*:*:*:*:*:*
-
cpe:2.3:a:amazon:aws_encryption_sdk:1.3.4:*:*:*:*:*:*:*
cpe:2.3:a:amazon:aws_encryption_sdk:1.3.4:*:*:*:*:*:*:*
-
cpe:2.3:a:amazon:aws_encryption_sdk:1.3.5:*:*:*:*:*:*:*
cpe:2.3:a:amazon:aws_encryption_sdk:1.3.5:*:*:*:*:*:*:*
-
cpe:2.3:a:amazon:aws_encryption_sdk:1.3.6:*:*:*:*:*:*:*
cpe:2.3:a:amazon:aws_encryption_sdk:1.3.6:*:*:*:*:*:*:*
-
cpe:2.3:a:amazon:aws_encryption_sdk:1.4.0:*:*:*:*:*:*:*
cpe:2.3:a:amazon:aws_encryption_sdk:1.4.0:*:*:*:*:*:*:*
-
cpe:2.3:a:amazon:aws_encryption_sdk:1.4.1:*:*:*:*:*:*:*
cpe:2.3:a:amazon:aws_encryption_sdk:1.4.1:*:*:*:*:*:*:*
-
cpe:2.3:a:amazon:aws_encryption_sdk:1.5.0:*:*:*:*:*:*:*
cpe:2.3:a:amazon:aws_encryption_sdk:1.5.0:*:*:*:*:*:*:*
-
cpe:2.3:a:amazon:aws_encryption_sdk:1.6.0:*:*:*:*:*:*:*
cpe:2.3:a:amazon:aws_encryption_sdk:1.6.0:*:*:*:*:*:*:*
-
cpe:2.3:a:amazon:aws_encryption_sdk:1.6.1:*:*:*:*:*:*:*
cpe:2.3:a:amazon:aws_encryption_sdk:1.6.1:*:*:*:*:*:*:*
-
cpe:2.3:a:amazon:aws_encryption_sdk:1.6.2:*:*:*:*:*:*:*
cpe:2.3:a:amazon:aws_encryption_sdk:1.6.2:*:*:*:*:*:*:*
-
cpe:2.3:a:amazon:aws_encryption_sdk:1.7.0:*:*:*:*:*:*:*
cpe:2.3:a:amazon:aws_encryption_sdk:1.7.0:*:*:*:*:*:*:*
-
cpe:2.3:a:amazon:aws_encryption_sdk:1.9.0:*:*:*:*:*:*:*
cpe:2.3:a:amazon:aws_encryption_sdk:1.9.0:*:*:*:*:*:*:*
-
cpe:2.3:a:amazon:aws_encryption_sdk:1.9.1:*:*:*:*:*:*:*
cpe:2.3:a:amazon:aws_encryption_sdk:1.9.1:*:*:*:*:*:*:*
-
cpe:2.3:a:amazon:aws_encryption_sdk:1.9.2:*:*:*:*:*:*:*
cpe:2.3:a:amazon:aws_encryption_sdk:1.9.2:*:*:*:*:*:*:*
CVSS3 Source
cve-coordination@google.com
CVSS3 Type
Secondary
CVSS3 Vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:N
Protect Your Infrastructure: Combat Critical CVE Threats
Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.