Heap corruption via failed session copy cleanup
Published Dec 20, 2021 · Updated Nov 3, 2025
Double free in Mbed TLS allows remote attackers to corrupt heap memory by triggering an out-of-memory session-copy failure. After ssl_session_copy leaves two structures pointing to the same ticket buffer, normal cleanup through mbedtls_ssl_session_free and mbedtls_ssl_free releases that buffer twice. Exploitation requires an allocation failure in mbedtls_ssl_set_session or mbedtls_ssl_get_session; the published consequence is heap corruption, not a demonstrated code-execution path.
Summary
What happened
Double free in Mbed TLS allows remote attackers to corrupt heap memory by triggering an out-of-memory session-copy failure. After ssl_session_copy leaves two structures pointing to the same ticket buffer, normal cleanup through mbedtls_ssl_session_free and mbedtls_ssl_free releases that buffer twice. Exploitation requires an allocation failure in mbedtls_ssl_set_session or mbedtls_ssl_get_session; the published consequence is heap corruption, not a demonstrated code-execution path.
The record
- CVE
- CVE-2021-44732
- Published
- Dec 20, 2021
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 20, 2021CVE publishedPublication date reported by the CVE source.
- Nov 3, 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.
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