The AWS S3 Crypto SDK sends an unencrypted hash of the plaintext alongside the ciphertext as a metadata field. This hash can be used to brute force the plaintext, if the hash is readable to the attacker. AWS now blocks this metadata field, but older SDK versions still send it.
Product
AWS github.com/aws/aws-sdk-go vulnerabilities
3 published CVES affecting AWS github.com/aws/aws-sdk-go, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 3
- Critical
- 0
- High
- 0
- Medium
- 2
- Low
- 1
- Unscored
- 0
- CISA KEV
- 0
Latest AWS github.com/aws/aws-sdk-go CVEs
Newest publication first
-
MediumCVSS 4.3 EPSS 0.51%
-
MediumCVSS 5.6 EPSS 0.35% PoC
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 a...
-
LowCVSS 2.5 EPSS 0.23% PoC
A vulnerability in the in-band key negotiation exists in the AWS S3 Crypto SDK for GoLang versions prior to V2. An attacker with write access to the targeted bucket can change the encryption algorithm of an object in the bucket, which can then allow them to change AES-GCM to AES-...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.