Deps.rs

aws-lc-rs 1.9.0

[![dependency status](https://deps.rs/crate/aws-lc-rs/1.9.0/status.svg)](https://deps.rs/crate/aws-lc-rs/1.9.0)

This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.

Crate aws-lc-rs

Dependencies

(6 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 aws-lc-fips-sys^0.12.00.13.13out of date
 aws-lc-sys ⚠️^0.21.00.39.0out of date
 mirai-annotations^1.12.01.12.0up to date
 paste^1.0.111.0.15up to date
 untrusted^0.7.10.9.0out of date
 zeroize^1.71.8.2up to date

Dev dependencies

(10 total, 6 outdated)

CrateRequiredLatestStatus
 cc=1.0.1051.2.57out of date
 clap^4.1.84.6.0up to date
 hex^0.4.30.4.3up to date
 home=0.5.50.5.12out of date
 lazy_static^1.4.01.5.0up to date
 proc-macro2^1.0.601.0.106up to date
 regex~1.9.61.12.3out of date
 regex-automata~0.3.90.4.14out of date
 regex-syntax~0.7.50.8.10out of date
 which^5.0.08.0.2out of date

Security Vulnerabilities

aws-lc-sys: Timing Side-Channel in AES-CCM Tag Verification in AWS-LC

RUSTSEC-2026-0045

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. aws-lc-sys contains code from AWS-LC. Applications using aws-lc-sys should upgrade to the most recent release of aws-lc-sys.

Workarounds

In the special cases of using AES-CCM with (M=4, L=2), (M=8, L=2), or (M=16, L=2), applications can workaround this issue by using AES-CCM through the EVP AEAD API using implementations EVP_aead_aes_128_ccm_bluetooth, EVP_aead_aes_128_ccm_bluetooth_8, and EVP_aead_aes_128_ccm_matter respectively.

Otherwise, there is no workaround and applications using aws-lc-sys should upgrade to the most recent release.

aws-lc-sys: CRL Distribution Point Scope Check Logic Error in AWS-LC

RUSTSEC-2026-0048

A logic error in CRL distribution point matching in AWS-LC allows a revoked certificate to bypass revocation checks during certificate validation, when the application enables CRL checking and uses partitioned CRLs with Issuing Distribution Point (IDP) extensions.

Customers of AWS services do not need to take action. aws-lc-sys contains code from AWS-LC. Applications using aws-lc-sys should upgrade to the most recent release of aws-lc-sys.

Workarounds

Applications can workaround this issue if they do not enable CRL checking (X509_V_FLAG_CRL_CHECK). Applications using complete (non-partitioned) CRLs without IDP extensions are also not affected.

Otherwise, there is no workaround and applications using aws-lc-sys should upgrade to the most recent releases of aws-lc-sys.