Memory exposure via uninitialized read_spv buffer
Published Dec 26, 2021 · Updated Aug 4, 2024
Use of uninitialized memory in ash before 0.33.1 allows context-dependent attackers to expose process memory through util::read_spv. The function passes an uninitialized buffer to a caller-supplied Read implementation, which can inspect its prior contents or report an incorrect byte count. Reachability requires consuming code to supply a hostile or incorrect Read implementation; consequences include bounded process-memory exposure and undefined behavior.
Summary
What happened
Use of uninitialized memory in ash before 0.33.1 allows context-dependent attackers to expose process memory through util::read_spv. The function passes an uninitialized buffer to a caller-supplied Read implementation, which can inspect its prior contents or report an incorrect byte count. Reachability requires consuming code to supply a hostile or incorrect Read implementation; consequences include bounded process-memory exposure and undefined behavior.
The record
- CVE
- CVE-2021-45688
- 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