CVE-2026-3337RUSTSEC-2026-0045GHSA-65P9-R9H6-22VJGHSA-FRMV-5GCM-JWXHRUSTSEC-2026-0043
Timing Side-Channel in AES-CCM Tag Verification in AWS-LC
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.69.0, 3.2.0, 0.38.0, 0.13.12
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Observable timing discrepancy in AES-CCM decryption in AWS-LC allows an unauthenticated user to potentially determine authentication tag validity via timing analysis. The impacted implementations are through the EVP CIPHER API: EVP_aes_128_ccm, EVP_aes_192_ccm, and EVP_aes_256_ccm. Customers of AWS services do not need to take action. Applications using AWS-LC should upgrade to AWS-LC version 1.69.0.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- AWS AWS-LC
From 1.21.0 · fixed in 1.69.0
- AWS AWS-LC-FIPS
From 3.0.0 · fixed in 3.2.0
- aws-lc-syscrates.io
From 0.14.0 · fixed in 0.38.0
- aws-lc-fips-syscrates.io
From 0.13.0 · fixed in 0.13.12