<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-01T14:57:59.967921+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-394x-vwmw-crm3</id>
    <title>GHSA-394x-vwmw-crm3 — AWS-LC X.509 Name Constraints Bypass via Wildcard/Unicode CN</title>
    <updated>2026-10-01T14:57:59.971077+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: aws-lc-sys</p>
<p>### Summary</p>
<p>AWS-LC is an open-source, general-purpose cryptographic library.</p>
<p>### Impact</p>
<p>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 `NAME_CONSTRAINTS_check_CN` to skip validation. However, `X509_check_host` accepts these CN values when no dNSName SAN is present, allowing certificates to bypass name constraints while still being used for hostname verification.</p>
<p>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.</p>
<p>### Impacted versions:</p>
<p>* aws-lc-sys &gt;= v0.32.0, &lt; v0.39.0</p>
<p>### Patches</p>
<p>The patch is included in aws-lc-sys v0.39.0.</p>
<p>### Workarounds</p>
<p>Applications that set `X509_CHECK_FLAG_NEVER_CHECK_SUBJECT` to disable CN fallback are not affected. Applications that only encounter certificates with dNSName SANs (standard for public WebPKI) are also not affected.</p>
<p>Otherwise, there is no workaround and applications using aws-lc-sys should upgrade to the most recent releases of aws-lc-sys.</p>
<p>### References</p>
<p>If you have any questions or comments about this advisory, we ask that you contact AWS Security via our [vulnerability reporting page](https://aws.amazon.com/security/vulnerability-reporting/) or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not cr…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-394x-vwmw-crm3"/>
  </entry>
</feed>
