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.
Weakness
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.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Aws-lc-fips-sys | Amazon | 0.13.0 (including) | 0.13.12 (excluding) |
| Aws-lc-sys | Amazon | 0.14.0 (including) | 0.38.0 (excluding) |
| Aws_libcrypto | Amazon | 1.21.0 (including) | 1.69.0 (excluding) |
| Aws_libcrypto | Amazon | 3.0.0 (including) | 3.2.0 (excluding) |
Related Attack Patterns
- https://cwe.mitre.org/data/definitions/462.html
- https://cwe.mitre.org/data/definitions/541.html
- https://cwe.mitre.org/data/definitions/580.html