CVE-2023-52353
First published: Sun Jan 21 2024(Updated: )
An issue was discovered in Mbed TLS through 3.5.1. In mbedtls_ssl_session_reset, the maximum negotiable TLS version is mishandled. For example, if the last connection negotiated TLS 1.2, then 1.2 becomes the new maximum.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| mbed TLS | <3.5.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2023-52353?
The severity of CVE-2023-52353 is rated as high due to the mishandling of maximum negotiable TLS versions.
How do I fix CVE-2023-52353?
To fix CVE-2023-52353, upgrade Mbed TLS to version 3.5.2 or later.
What versions of Mbed TLS are affected by CVE-2023-52353?
Mbed TLS versions up to 3.5.1 are affected by CVE-2023-52353.
What types of applications are impacted by CVE-2023-52353?
Applications using Mbed TLS for secure communication are impacted by CVE-2023-52353.
Can CVE-2023-52353 lead to security breaches?
Yes, CVE-2023-52353 can potentially allow attackers to exploit the mishandling of TLS versions, leading to downgrade attacks.
- agent/references
- agent/type
- agent/description
- agent/first-publish-date
- agent/author
- agent/event
- agent/severity
- agent/weakness
- agent/remedy
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/arm
- canonical/mbed tls