<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent sightings.</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent sightings.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 04 May 2026 19:21:00 +0000</lastBuildDate>
    <item>
      <title>d2213fa6-b906-4965-9213-1cb66e93534a</title>
      <link>https://vulnerability.circl.lu/sighting/d2213fa6-b906-4965-9213-1cb66e93534a/export</link>
      <description>{"uuid": "d2213fa6-b906-4965-9213-1cb66e93534a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45159", "type": "seen", "source": "https://t.me/cvedetector/4938", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45159 - Mbed TLS Invalid Certificate Validation in TLS 1.3 Client Authentication\", \n  \"Content\": \"CVE ID : CVE-2024-45159 \nPublished : Sept. 5, 2024, 7:15 p.m. | 39\u00a0minutes ago \nDescription : An issue was discovered in Mbed TLS 3.x before 3.6.1. With TLS 1.3, when a server enables optional authentication of the client, if the client-provided certificate does not have appropriate values in if keyUsage or extKeyUsage extensions, then the return value of mbedtls_ssl_get_verify_result() would incorrectly have the MBEDTLS_X509_BADCERT_KEY_USAGE and MBEDTLS_X509_BADCERT_KEY_USAGE bits clear. As a result, an attacker that had a certificate valid for uses other than TLS client authentication would nonetheless be able to use it for TLS client authentication. Only TLS 1.3 servers were affected, and only with optional authentication (with required authentication, the handshake would be aborted with a fatal alert). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-05T22:13:22.000000Z"}</description>
      <content:encoded>{"uuid": "d2213fa6-b906-4965-9213-1cb66e93534a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45159", "type": "seen", "source": "https://t.me/cvedetector/4938", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45159 - Mbed TLS Invalid Certificate Validation in TLS 1.3 Client Authentication\", \n  \"Content\": \"CVE ID : CVE-2024-45159 \nPublished : Sept. 5, 2024, 7:15 p.m. | 39\u00a0minutes ago \nDescription : An issue was discovered in Mbed TLS 3.x before 3.6.1. With TLS 1.3, when a server enables optional authentication of the client, if the client-provided certificate does not have appropriate values in if keyUsage or extKeyUsage extensions, then the return value of mbedtls_ssl_get_verify_result() would incorrectly have the MBEDTLS_X509_BADCERT_KEY_USAGE and MBEDTLS_X509_BADCERT_KEY_USAGE bits clear. As a result, an attacker that had a certificate valid for uses other than TLS client authentication would nonetheless be able to use it for TLS client authentication. Only TLS 1.3 servers were affected, and only with optional authentication (with required authentication, the handshake would be aborted with a fatal alert). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-05T22:13:22.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/d2213fa6-b906-4965-9213-1cb66e93534a/export</guid>
      <pubDate>Thu, 05 Sep 2024 22:13:22 +0000</pubDate>
    </item>
  </channel>
</rss>
