Skip to main content
EPSS 0.4%top 68%

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...

0
Medium
Published: 11/28/2024 (11/28/2024, 00:00:00 UTC)
Source: GCVE Database
Vendor/Project: Microsoft Security Response Center
Product: Microsoft

Description

CVE-2024-45159 is a vulnerability in Mbed TLS versions 3.x prior to 3.6.1 related to TLS 1.3 client certificate authentication. When a server enables optional client authentication, the client certificate's keyUsage or extKeyUsage extensions may not be properly validated, potentially leading to incorrect authentication decisions. The issue affects Microsoft products including Azure Linux and CBL Mariner 2.0. No CVSS score is provided, and no known exploits are reported in the wild. Patch status is not confirmed due to lack of vendor advisory details.

Affected software

Affected versions
=2.0

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/07/2026, 19:27:45 UTC

Technical Analysis

This vulnerability in Mbed TLS before version 3.6.1 involves improper validation of client certificates during TLS 1.3 optional client authentication. Specifically, if the client certificate lacks appropriate values in the keyUsage or extendedKeyUsage extensions, the server may not correctly enforce authentication requirements. The flaw is identified under CWE-295 (Improper Certificate Validation). The affected products include Microsoft Azure Linux and CBL Mariner 2.0 distributions. No patch or remediation details are provided in the available data.

Potential Impact

The impact is that a server using Mbed TLS for TLS 1.3 optional client authentication might accept client certificates that do not meet the expected usage constraints, potentially weakening authentication guarantees. This could allow unauthorized clients to be accepted if the certificate validation is insufficient. No evidence of active exploitation is reported.

Mitigation Recommendations

Patch status is not yet confirmed — check the Microsoft Security Response Center advisory for current remediation guidance. Until a fix is available, administrators should consider disabling optional client authentication or implementing additional certificate validation controls if feasible.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Csaf Category
csaf_vex
Csaf Version
2.0
Publisher
Microsoft Security Response Center
Advisory Id
msrc_CVE-2024-45159
Cve Count
1

Threat ID: 6a998f63acd9273b49193440

Added to database: 09/03/2026, 15:16:51 UTC

Last enriched: 09/07/2026, 19:27:45 UTC

Last updated: 09/10/2026, 19:36:48 UTC

Views: 9

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses