aws-samples / aws-samples/sample-code-for-a-secure-vault-using-aws-nitro-enclaves
RUSTSEC-2026-0048: CRL Distribution Point Scope Check Logic Error in AWS-LC
- Dominant language
- Rust
- Stars
- 9
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
> CRL Distribution Point Scope Check Logic Error in AWS-LC
| Details | |
| ------------------- | ---------------------------------------------- |
| Package | `aws-lc-sys` |
| Version | `0.35.0` |
| URL | [https://aws.amazon.com/security/security-bulletins/2026-010-AWS](https://aws.amazon.com/security/security-bulletins/2026-010-AWS) |
| Date | 2026-03-19 |
| Patched versions | `>=0.39.0` |
| Unaffected versions | `<0.15.0` |
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`.
See [advisory page](https://rustsec.org/advisories/RUSTSEC-2026-0048.html) for additional details.
Contributor guide
Research direction
Locate the repository's Cargo.toml and Cargo.lock entries for aws-lc-sys, then review how dependencies are checked and updated. Raise aws-lc-sys from 0.35.0 to at least 0.39.0 and run the repository's available Cargo checks or tests; done means the dependency resolves to a patched version without breaking the project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100