Mbed TlsApplication · Arm

CVE-2024-23775

HIGH · 7.5 CVSS v3.1 Published 2024-01-31
Fix available
A fix is available. Upgrade to 2.28.7 / 3.5.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Integer Overflow vulnerability in Mbed TLS 2.x before 2.28.7 and 3.x before 3.5.2, allows attackers to cause a denial of service (DoS) via mbedtls_x509_set_extension().

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Integer overflow vulnerability in mbedtls_x509_set_extension() function in Mbed TLS versions prior to 2.28.7 (2.x) and 3.5.2 (3.x). The flaw allows attackers to trigger a denial of service through improper integer handling when processing X.509 certificate extensions.

MitigationUpgrade Mbed TLS library to version 2.28.7 or later for 2.x branches, or version 3.5.2 or later for 3.x branches.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mbed TlsApplication
Affected:>= 2.0.0, < 2.28.7
Mbed TlsApplication
Affected:>= 3.0.0, < 3.5.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Mbed TLS library in use
    Locate the Mbed TLS library file or package installed in the system. This may be a shared library file (such as libmbedtls.so on Linux or mbedtls.dll on Windows), or a package managed by the system's package manager.
    Affected if The library cannot be found or is not Mbed TLS
  2. Determine the installed Mbed TLS version
    Use the system's package manager, library versioning tools, or any version reporting mechanism provided by the application using Mbed TLS to retrieve the exact version number.
    Affected if The version is less than 2.28.7 for 2.x branches, or less than 3.5.2 for 3.x branches
  3. Confirm the application uses X.509 certificate handling
    Inspect the application code or configuration to determine if Mbed TLS X.509 functionality is being used, particularly functions that process certificate extensions.
    Affected if X.509 certificate extension processing is performed using the affected code path
  4. Check if certificate extensions are processed from untrusted sources
    Review whether the application processes X.509 certificates from external or untrusted sources, as the integer overflow occurs when setting certificate extensions.
    Affected if The application processes certificate extensions from external or untrusted sources without additional validation

You are affected if your Mbed TLS version is below 2.28.7 (for 2.x) or below 3.5.2 (for 3.x) AND your application processes X.509 certificate extensions from external sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.28.7 / 3.5.2 or later
Fixed in 2.28.73.5.2
Interim mitigation

Upgrade Mbed TLS library to version 2.28.7 or later for 2.x branches, or version 3.5.2 or later for 3.x branches.

Recommended fix High confidence

Mbed TLS 2.28.7 (for 2.x line) or Mbed TLS 3.5.2 (for 3.x line)

  1. Identify current Mbed TLS version by checking library headers or build configuration
  2. For Mbed TLS 2.x line: upgrade to version 2.28.7
  3. For Mbed TLS 3.x line: upgrade to version 3.5.2
  4. Verify the installed version matches the target fixed release using mbedtls_version_get_number() or equivalent
  5. Test that certificate handling functionality using mbedtls_x509_set_extension() continues to work correctly
Caveat Point releases within the same major version are typically backward compatible; no breaking changes expected for this security fix

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mbed Tls Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23775 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-23775 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data