Timing Side-Channel in AES-CCM Tag Verification in AWS-LC
AWS-LC · AWS-LC-FIPS
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| aws-lc-sys crates.io |
|
|
| aws-lc-fips-sys crates.io |
|
|
AWS-LC · AWS-LC-FIPS
| Product | Affected | Fixed in |
|---|---|---|
| aws-lc-sys crates.io |
|
|
| aws-lc-fips-sys crates.io |
|
|
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.
From the CVE record · AMZN
AES-CCM decryption through the EVP CIPHER API in AWS-LC has an observable timing discrepancy. An unauthenticated user may be able to determine authentication tag validity through timing analysis.
Teams using AWS-LC or AWS-LC-FIPS should check applications using aws-lc-sys versions >=0.14.0 <0.38.0 or aws-lc-fips-sys versions >=0.13.0 <0.13.12.