Aws Encryption SDK vulnerabilitiesRanked by how likely they are to be used.
Aws Encryption SDK is made by Amazon. We track 2 published vulnerabilities in it, across 27 versions. None of them is on the list of flaws known to be exploited today. If you run Aws Encryption SDK, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Aws Encryption SDK vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Aws Encryption SDK's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Aws Encryption SDK flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 0.4%CVE-2020-8897High
A weak robustness vulnerability exists in the AWS Encryption SDKs for Java, Python, C and Javalcript prior to versions 2.0.0.
- 0.2%CVE-2024-23680Medium
AWS Encryption SDK for Java versions 2.0.0 to 2.2.0 and less than 1.9.0 incorrectly validates some invalid ECDSA signatures.
Running Aws Encryption SDK? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Aws Encryption SDK on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 2 published vulnerabilities listed under the name Aws Encryption SDK, across 27 versions.
None of Aws Encryption SDK's vulnerabilities is on the list of flaws known to be exploited today.
Create a EdgeProtect account and track Aws Encryption SDK. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.