VYPR
High severity7.5NVD Advisory· Published Jan 31, 2024· Updated Jun 5, 2026

CVE-2024-23775

CVE-2024-23775

Description

Integer overflow in Mbed TLS 2.x before 2.28.7 and 3.x before 3.5.2 allows a DoS via heap buffer overflow in mbedtls_x509_set_extension().

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Integer overflow in Mbed TLS 2.x before 2.28.7 and 3.x before 3.5.2 allows a DoS via heap buffer overflow in mbedtls_x509_set_extension().

Vulnerability

An integer overflow vulnerability exists in Mbed TLS versions 2.x before 2.28.7 and 3.x before 3.5.2. When parsing or writing x509 extensions, the function mbedtls_x509_set_extension() fails to validate the length input, which can lead to an integer overflow. This results in the allocation of a zero-length buffer on the heap, and subsequent copy of extension data into that buffer causes a heap buffer overflow [3].

Exploitation

An attacker can trigger the vulnerability by providing a crafted x509 extension with a specific length that causes the integer overflow. No special privileges are required beyond the ability to supply input to the extension parsing logic. The function mbedtls_x509_set_extension() is reachable when processing X.509 certificates or CSRs. A concrete sequence involves passing a length value that causes the internal arithmetic to wrap, resulting in a small or zero buffer allocation, followed by copying data that exceeds that allocation [3].

Impact

Successful exploitation leads to a heap buffer overflow, which typically results in a segmentation fault (segfault), causing a denial of service (DoS) of the application using Mbed TLS [1][3]. The impact is limited to availability (DoS) and does not provide code execution or information disclosure according to the available references.

Mitigation

Users should upgrade to Mbed TLS 2.28.7 (2.x branch) or 3.5.2 (3.x branch) as these versions contain the fix [3]. A workaround is to ensure that a length of SIZE_MAX cannot be passed into mbedtls_x509_set_extension(), though upgrading is strongly recommended [3]. No CISA KEV listing was identified for this CVE at the time of writing.

AI Insight generated on May 25, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2
  • Mbed TLS/Mbed TLSdescription
  • Arm/MbedTLSllm-fuzzy
    Range: <2.28.7, <3.5.2

Patches

2
daca7a3979c2

Update BRANCHES.md

https://github.com/armmbed/mbedtlsDave RodgmanJan 24, 2024via osv
1 file changed · +1 1
  • BRANCHES.md+1 1 modified
    @@ -106,6 +106,6 @@ The following branches are currently maintained:
     - [`development`](https://github.com/Mbed-TLS/mbedtls/)
     - [`mbedtls-2.28`](https://github.com/Mbed-TLS/mbedtls/tree/mbedtls-2.28)
      maintained until at least the end of 2024, see
    -  <https://github.com/Mbed-TLS/mbedtls/releases/tag/v2.28.6>.
    +  <https://github.com/Mbed-TLS/mbedtls/releases/tag/v2.28.7>.
     
     Users are urged to always use the latest version of a maintained branch.
    
555f84735aec

Update BRANCHES.md

https://github.com/armmbed/mbedtlsDave RodgmanJan 22, 2024via osv
1 file changed · +1 1
  • BRANCHES.md+1 1 modified
    @@ -76,6 +76,6 @@ The following branches are currently maintained:
     - [`development`](https://github.com/Mbed-TLS/mbedtls/)
     - [`mbedtls-2.28`](https://github.com/Mbed-TLS/mbedtls/tree/mbedtls-2.28)
      maintained until at least the end of 2024, see
    -  <https://github.com/Mbed-TLS/mbedtls/releases/tag/v2.28.6>.
    +  <https://github.com/Mbed-TLS/mbedtls/releases/tag/v2.28.7>.
     
     Users are urged to always use the latest version of a maintained branch.
    

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

5

News mentions

0

No linked articles in our index yet.