https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 06:58:39 +0000 https://cve.radiocsirt.org/vuln/cve-2020-8897 <p><strong>Affected:</strong> Amazon AWS SDK</p> <p>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.</p> <p><strong>Affected:</strong> Amazon AWS SDK</p> <p>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.</p> https://cve.radiocsirt.org/vuln/cve-2020-8897 https://cve.radiocsirt.org/vuln/ghsa-wqgp-vphw-hphf <p><strong>Affected:</strong> Maven: com.amazonaws:aws-encryption-sdk-java, PyPI: aws-encryption-sdk</p> <p>Authors: Thai &#34;[thaidn](https://twitter.com/xorninja)&#34; Duong</p> <p># Summary</p> <p>The following security vulnerabilities was discovered and reported to Amazon, affecting AWS KMS and all versions of [AWS Encryption SDKs](https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/introduction.html) prior to version 2.0.0:</p> <p>* **Information leakage**: an attacker can create ciphertexts that would leak the user’s AWS account ID, encryption context, user agent, and IP address upon decryption * **Ciphertext forgery**: an attacker can create ciphertexts that are accepted by other users * **Robustness**: an attacker can create ciphertexts that decrypt to different plaintexts for different users</p> <p>The first two bugs are somewhat surprising because they show that the ciphertext format can lead to vulnerabilities. These bugs (and the infamous [alg: &#34;None&#34;](https://auth0.com/blog/critical-vulnerabilities-in-json-web-token-libraries/) bugs in JWT) belong to a class of vulnerabilities called **in-band protocol negotiation**. This is the second time we’ve found in-band protocol negotiation vulnerabilities in AWS cryptography libraries; see this [bug](https://github.com/google/security-research/security/advisories/GHSA-7f33-f4f5-xwgw) in S3 Crypto SDK discovered by my colleague Sophie Schmieg.</p> <p>In JWT and S3 SDK the culprit is the algorithm field—here it is the key ID. Because the key ID is used to determine which decryption key to use, it can’t be meaningfully authenticated despite being under…</p> <p><strong>Affected:</strong> Maven: com.amazonaws:aws-encryption-sdk-java, PyPI: aws-encryption-sdk</p> <p>Authors: Thai &#34;[thaidn](https://twitter.com/xorninja)&#34; Duong</p> <p># Summary</p> <p>The following security vulnerabilities was discovered and reported to Amazon, affecting AWS KMS and all versions of [AWS Encryption SDKs](https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/introduction.html) prior to version 2.0.0:</p> <p>* **Information leakage**: an attacker can create ciphertexts that would leak the user’s AWS account ID, encryption context, user agent, and IP address upon decryption * **Ciphertext forgery**: an attacker can create ciphertexts that are accepted by other users * **Robustness**: an attacker can create ciphertexts that decrypt to different plaintexts for different users</p> <p>The first two bugs are somewhat surprising because they show that the ciphertext format can lead to vulnerabilities. These bugs (and the infamous [alg: &#34;None&#34;](https://auth0.com/blog/critical-vulnerabilities-in-json-web-token-libraries/) bugs in JWT) belong to a class of vulnerabilities called **in-band protocol negotiation**. This is the second time we’ve found in-band protocol negotiation vulnerabilities in AWS cryptography libraries; see this [bug](https://github.com/google/security-research/security/advisories/GHSA-7f33-f4f5-xwgw) in S3 Crypto SDK discovered by my colleague Sophie Schmieg.</p> <p>In JWT and S3 SDK the culprit is the algorithm field—here it is the key ID. Because the key ID is used to determine which decryption key to use, it can’t be meaningfully authenticated despite being under…</p> https://cve.radiocsirt.org/vuln/ghsa-wqgp-vphw-hphf