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
5 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
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.39.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
AWS-LC is an open-source, general-purpose cryptographic library. Impact A logic error in CN (Common Name) validation allows certificates with wildcard or raw UTF-8 Unicode CN values to bypass name constraints enforcement. The cn2dnsid function does not recognize these CN patterns as valid DNS identifiers, causing NAMECONSTRAINTScheckCN to skip validation. However, X509checkhost accepts these CN values when no dNSName SAN is present, allowing certificates to bypass name constraints while still being used for hostname verification. Customers of AWS services do not need to take action. Applications using aws-lc-sys should upgrade to the most recent release of aws-lc-sys. Impacted versions: aws-lc-sys = v0.32.0, < v0.39.0 Patches The patch is included in aws-lc-sys v0.39.0. Workarounds Applications that set X509CHECKFLAGNEVERCHECKSUBJECT to disable CN fallback are not affected. Applications that only encounter certificates with dNSName SANs (standard for public WebPKI) are also…
Recommended action: Upgrade to 0.39.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
AWS-LC is an open-source, general-purpose cryptographic library. Impact Improper signature validation in PKCS7verify() in AWS-LC allows an unauthenticated user to bypass signature verification when processing PKCS7 objects with Authenticated Attributes. 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. Impacted versions: aws-lc-sys versions: = 0.24.0, < 0.38.0 Patches The patch is included in v0.38.0 Workarounds There is no workaround. Applications using aws-lc-sys should upgrade to the most recent release of aws-lc-sys. Resources If there are any questions or comments about this advisory, contact [AWS/Amazon] Security via the vulnerability reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.
Recommended action: Upgrade to 0.38.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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.38.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
AWS-LC is an open-source, general-purpose cryptographic library. Impact Improper certificate validation in PKCS7verify() in AWS-LC allows an unauthenticated user to bypass certificate chain verification when processing PKCS7 objects with multiple signers, except the final signer. 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. Impacted versions: aws-lc-sys versions: = 0.24.0, < 0.38.0 Patches The patch is included in v0.38.0 Workarounds There is no workaround. Applications using aws-lc-sys should upgrade to the most recent release of aws-lc-sys. Resources If there are any questions or comments about this advisory, contact [AWS/Amazon] Security via the vulnerability reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. Acknowledgement AWS-LC would like to thank Joshua Rogers…
Recommended action: Upgrade to 0.38.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.