Plaintext retention via incomplete buffer zeroization
Published Aug 23, 2021 · Updated Aug 4, 2024
Incomplete data removal in Mbed TLS before 2.24.0 allows attackers to cause unused application plaintext to remain in process memory. The mbedtls_ssl_read function fails to zero unused portions of its plaintext buffer after application data is read, leaving earlier bytes resident. The condition occurs when an application receives TLS plaintext through this API; public records do not identify a method for attackers to read the retained bytes.
Summary
What happened
Incomplete data removal in Mbed TLS before 2.24.0 allows attackers to cause unused application plaintext to remain in process memory. The mbedtls_ssl_read function fails to zero unused portions of its plaintext buffer after application data is read, leaving earlier bytes resident. The condition occurs when an application receives TLS plaintext through this API; public records do not identify a method for attackers to read the retained bytes.
The record
- CVE
- CVE-2020-36476
- Published
- Aug 23, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-212
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 23, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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