Memory exposure via uninitialized read buffer
Published Dec 26, 2021 · Updated Aug 4, 2024
Memory exposure in Rust columnar 0.0.19 and earlier allows context-dependent attackers to read uninitialized buffer contents. ColumnarReadExt::read_typed_vec sets a vector length before initialization, then passes its backing slice to a caller-supplied Read implementation. Reachability requires application code to invoke the method with an attacker-controlled Read implementation; disclosure of residual process memory or a process crash can result.
Summary
What happened
Memory exposure in Rust columnar 0.0.19 and earlier allows context-dependent attackers to read uninitialized buffer contents. ColumnarReadExt::read_typed_vec sets a vector length before initialization, then passes its backing slice to a caller-supplied Read implementation. Reachability requires application code to invoke the method with an attacker-controlled Read implementation; disclosure of residual process memory or a process crash can result.
The record
- CVE
- CVE-2021-45685
- 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.
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