Heap corruption via DTLS CID length handling
Published Dec 15, 2022 · Updated Apr 21, 2025
Mbed TLS before 2.28.2 and 3.x before 3.3.0 allows remote attackers to corrupt heap memory via malformed DTLS Connection ID lengths. DTLS processing trusts inconsistent MBEDTLS_SSL_CID_IN_LEN_MAX and MBEDTLS_SSL_CID_OUT_LEN_MAX values when Connection IDs are enabled, causing heap overreads or overwrites. Exploitation requires a reachable DTLS endpoint built with the feature and oversized input-length configuration; malformed network traffic can crash the service or disclose or alter adjacent memory.
Summary
What happened
Mbed TLS before 2.28.2 and 3.x before 3.3.0 allows remote attackers to corrupt heap memory via malformed DTLS Connection ID lengths. DTLS processing trusts inconsistent MBEDTLS_SSL_CID_IN_LEN_MAX and MBEDTLS_SSL_CID_OUT_LEN_MAX values when Connection IDs are enabled, causing heap overreads or overwrites. Exploitation requires a reachable DTLS endpoint built with the feature and oversized input-length configuration; malformed network traffic can crash the service or disclose or alter adjacent memory.
The record
- CVE
- CVE-2022-46393
- Published
- Dec 15, 2022
- Updated
- Apr 21, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, CWE-787, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 15, 2022CVE publishedPublication date reported by the CVE source.
- Apr 21, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo