Tag-validity disclosure via variable-time comparison
Published Mar 2, 2026 · Updated Mar 2, 2026
An AES-CCM timing side channel in AWS-LC 1.21.0 through 1.68.0 and AWS-LC-FIPS 3.0.0 through 3.1.0 allows remote attackers to infer tag validity. The EVP_aes_128_ccm, EVP_aes_192_ccm, and EVP_aes_256_ccm decrypt paths use OPENSSL_memcmp instead of constant-time CRYPTO_memcmp to verify supplied tags. The caller must expose repeated AES-CCM decryptions and observable response timing; successful analysis reveals whether submitted tags are valid.
Summary
What happened
An AES-CCM timing side channel in AWS-LC 1.21.0 through 1.68.0 and AWS-LC-FIPS 3.0.0 through 3.1.0 allows remote attackers to infer tag validity. The EVP_aes_128_ccm, EVP_aes_192_ccm, and EVP_aes_256_ccm decrypt paths use OPENSSL_memcmp instead of constant-time CRYPTO_memcmp to verify supplied tags. The caller must expose repeated AES-CCM decryptions and observable response timing; successful analysis reveals whether submitted tags are valid.
The record
- CVE
- CVE-2026-3337
- Published
- Mar 2, 2026
- Updated
- Mar 2, 2026
- Vendor
- Amazon Web Services
- Product
- AWS-LC
- Classifications
- CWE-208
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 2, 2026CVE publishedPublication date reported by the CVE source.
- Mar 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.21.0 <1.69.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo