Timing Side-Channel in AES-CCM Tag Verification in AWS-LC
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 3.2.0, 1.69.0, aws-lc-fips-sys 0.13.12 and 1 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| AWS | >=3.0.0 <3.2.0, >=1.21.0 <1.69.0 | 3.2.0, 1.69.0 | |
| cargo: aws-lc-fips-sys | >=0.13.0 <0.13.12 | 0.13.12 | |
| cargo: aws-lc-sys | >=0.14.0 <0.38.0 | 0.38.0 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in aws-lc-fips-sys (Cargo), strongest first
Embed
A live severity badge for an advisory, README or ticket