Aws S3 Crypto SDK vulnerabilitiesRanked by how likely they are to be used.
Aws S3 Crypto SDK is made by Amazon. We track 2 published vulnerabilities in it, across 2 versions. None of them is on the list of flaws known to be exploited today. If you run Aws S3 Crypto SDK, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Aws S3 Crypto SDK vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Aws S3 Crypto SDK's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Aws S3 Crypto 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.3%CVE-2020-8911Medium
A padding oracle vulnerability exists in the AWS S3 Crypto SDK for GoLang versions prior to V2.
- 0.2%
A vulnerability in the in-band key negotiation exists in the AWS S3 Crypto SDK for GoLang versions prior to V2.
Running Aws S3 Crypto 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 padding oracle vulnerability exists in the AWS S3 Crypto SDK for GoLang versions prior to V2. The SDK allows users to encrypt files with AES-CBC without computing a Message Authentication Code (MAC), which then allows an attacker who has write access to the target's S3 bucket and can observe whether or not an endpoint with access to the key can decrypt a file, they can reconstruct the plaintext with (on average) 128*length (plaintext) queries to the endpoint, by exploiting CBC's ability to manipulate the bytes of the next block and PKCS5 padding errors. It is recommended to update your SDK to V2 or later, and re-encrypt your files.
- Matched to
- Aws S3 Crypto 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 S3 Crypto SDK, across 2 versions.
None of Aws S3 Crypto SDK's vulnerabilities is on the list of flaws known to be exploited today.
Create a EdgeProtect account and track Aws S3 Crypto 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.