CVE-2026-3337
Timing Side-Channel in AWS-LC AES-CCM Allows Tag Validation
Publication date: 2026-03-02
Last updated on: 2026-03-11
Assigner: AMZN
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| amazon | aws_libcrypto | From 1.21.0 (inc) to 1.69.0 (exc) |
| amazon | aws_libcrypto | From 3.0.0 (inc) to 3.2.0 (exc) |
| amazon | aws-lc-fips-sys | From 0.13.0 (inc) to 0.13.12 (exc) |
| amazon | aws-lc-sys | From 0.14.0 (inc) to 0.38.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-208 | Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability involves an observable timing discrepancy in the AES-CCM decryption process within AWS-LC. Specifically, an unauthenticated user can potentially determine whether an authentication tag is valid by analyzing the time it takes to perform decryption.
The affected implementations are those using the EVP CIPHER API functions: EVP_aes_128_ccm, EVP_aes_192_ccm, and EVP_aes_256_ccm.
How can this vulnerability impact me? :
An attacker exploiting this vulnerability could use timing analysis to determine the validity of authentication tags without authentication. This could potentially lead to information disclosure or facilitate further cryptographic attacks.
However, customers of AWS services do not need to take any action, and applications using AWS-LC should upgrade to version 1.69.0 to mitigate this issue.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
Applications using AWS-LC should upgrade to AWS-LC version 1.69.0 to mitigate this vulnerability.
Customers of AWS services do not need to take any action.