aws-samples / aws-samples/sample-code-for-a-secure-vault-using-aws-nitro-enclaves
RUSTSEC-2026-0104: Reachable panic in certificate revocation list parsing
- Dominant language
- Rust
- Stars
- 9
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
> Reachable panic in certificate revocation list parsing
| Details | |
| ------------------- | ---------------------------------------------- |
| Package | `rustls-webpki` |
| Version | `0.103.8` |
| Date | 2026-04-22 |
| Patched versions | `>=0.103.13, <0.104.0-alpha.1,>=0.104.0-alpha.7` |
A panic was reachable when parsing certificate revocation lists via [`BorrowedCertRevocationList::from_der`]
or [`OwnedCertRevocationList::from_der`]. This was the result of mishandling a syntactically valid empty
`BIT STRING` appearing in the `onlySomeReasons` element of a `IssuingDistributionPoint` CRL extension.
This panic is reachable prior to a CRL's signature being verified.
Applications that do not use CRLs are not affected.
Thank you to @tynus3 for the report.
See [advisory page](https://rustsec.org/advisories/RUSTSEC-2026-0104.html) for additional details.
Contributor guide
Research direction
Start with the linked RustSec advisory and review how this repository declares its rustls-webpki dependency. Check whether the affected CRL parsing paths using BorrowedCertRevocationList::from_der or OwnedCertRevocationList::from_der are relevant, then verify that the dependency is on a patched version and that the project’s checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100