Memory exposure via uninitialized Read buffers
Published Dec 26, 2021 · Updated Aug 4, 2024
Memory unsafety in acc_reader 2.0.0 and earlier allows attackers to expose uninitialized memory through a user-provided Read implementation. fill_buf and read_up_to extend a Vec with set_len before passing the new region to Read, allowing safe caller code to inspect bytes that were never initialized. Exploitation requires a caller-controlled Read implementation and can disclose process memory or trigger undefined behavior in the consuming application.
Summary
What happened
Memory unsafety in acc_reader 2.0.0 and earlier allows attackers to expose uninitialized memory through a user-provided Read implementation. fill_buf and read_up_to extend a Vec with set_len before passing the new region to Read, allowing safe caller code to inspect bytes that were never initialized. Exploitation requires a caller-controlled Read implementation and can disclose process memory or trigger undefined behavior in the consuming application.
The record
- CVE
- CVE-2020-36514
- Published
- Dec 26, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-908
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 26, 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