Skip to content

← Public intelligence

crates.io package

aws-lc-fips-sys

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.4crates.ioPublished

    CRL Distribution Point Scope Check Logic Error in AWS-LC

    GHSA-9f94-5g5w-gf6r

    Affected
    • crates.io aws-lc-fips-sys >= 0.13.0, < 0.13.13
    Fixed in
    0.13.13· Vendor fix available
    Issue
    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…

    Recommended action: Upgrade to 0.13.13 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 8.2crates.ioPublished

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

    GHSA-65p9-r9h6-22vj

    Affected
    • crates.io aws-lc-fips-sys >= 0.13.0, < 0.13.12
    Fixed in
    0.13.12· Vendor fix available
    Issue
    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…

    Recommended action: Upgrade to 0.13.12 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →