Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.2

AWS-LC has Timing Side-Channel in AES-CCM Tag Verification

GHSA-65p9-r9h6-22vj

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (aws-lc-sys 0.38.0; aws-lc-fips-sys 0.13.12), 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.14.0, < 0.38.0
    Fixed in
    0.38.0

  • crates.io aws-lc-fips-sys

    Affected
    >= 0.13.0, < 0.13.12
    Fixed in
    0.13.12

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.2 · CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N · score source
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 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: EVPaes128ccm, EVPaes192ccm, and EVPaes256ccm. 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 versions: = 0.14.0, < 0.38.0 - aws-lc-fips-sys versions: = v0.13.0, < 0.13.12. Patches The patch is included in aws-lc-sys v.0.38.0 and aws-lc-fips-sys v0.13.12. 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…

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

    Published from ghsa record GHSA-65p9-r9h6-22vj

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-65p9-r9h6-22vj

Advisory: AWS-LC has Timing Side-Channel in AES-CCM Tag Verification
IDs: GHSA-65p9-r9h6-22vj
Record: https://patchnext.com/advisories/ghsa-65p9-r9h6-22vj (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 8.2)
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.38.0; aws-lc-fips-sys 0.13.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io aws-lc-sys: affected >= 0.14.0, < 0.38.0; fixed in 0.38.0
- crates.io aws-lc-fips-sys: affected >= 0.13.0, < 0.13.12; fixed in 0.13.12

## 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-65p9-r9h6-22vj (GitHub-reviewed advisory GHSA-65p9-r9h6-22vj lists affected ranges: crates.io aws-lc-sys >=0.14.0 =0.13.0 <0.13.12)

Commands are suggestions: review each one before running it.

Loading voting…