Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.4

CRL Distribution Point Scope Check Logic Error in AWS-LC

GHSA-9f94-5g5w-gf6r

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (aws-lc-sys 0.39.0; aws-lc-fips-sys 0.13.13), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • crates.io aws-lc-sys

    Affected
    >= 0.15.0, < 0.39.0
    Fixed in
    0.39.0

  • crates.io aws-lc-fips-sys

    Affected
    >= 0.13.0, < 0.13.13
    Fixed in
    0.13.13

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.4 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary AWS-LC is an open-source, general-purpose cryptographic library. Impact 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 and aws-lc-fips-sys contain code from AWS-LC. Applications using aws-lc-sys or aws-lc-fips-sys should upgrade to the most recent releases of aws-lc-sys or aws-lc-fips-sys. Impacted versions: aws-lc-sys = v0.15.0, < v0.39.0 aws-lc-fips-sys = v0.13.0, < v0.13.13 Patches The patch is included in aws-lc-sys v0.39.0 and aws-lc-fips-sys v0.13.13. Workarounds Applications can workaround this issue if they do not enable CRL checking (X509VFLAGCRLCHECK). Applications using complete (non-partitioned) CRLs without IDP extensions are also not affected. Otherwise, there is no workaround and…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-9f94-5g5w-gf6r

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-9f94-5g5w-gf6r

Advisory: CRL Distribution Point Scope Check Logic Error in AWS-LC
IDs: GHSA-9f94-5g5w-gf6r
Record: https://patchnext.com/advisories/ghsa-9f94-5g5w-gf6r (revision 1, source checked 26 Oct 2026, 15:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: aws-lc-sys 0.39.0; aws-lc-fips-sys 0.13.13. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io aws-lc-sys: affected >= 0.15.0, < 0.39.0; fixed in 0.39.0
- crates.io aws-lc-fips-sys: affected >= 0.13.0, < 0.13.13; fixed in 0.13.13

## Suggested inspection (read-only)
- crates.io aws-lc-sys: check the installed version with your package manager.
- crates.io aws-lc-fips-sys: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on aws-lc-sys, aws-lc-fips-sys.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9f94-5g5w-gf6r (GitHub-reviewed advisory GHSA-9f94-5g5w-gf6r lists affected ranges: crates.io aws-lc-fips-sys >=0.13.0 =0.15.0 <0.39.0)

Commands are suggestions: review each one before running it.

Loading voting…