Memory disclosure via uninitialized buffer
Published Feb 9, 2021 · Updated Aug 3, 2024
Memory exposure in the Rust postscript crate before 0.14.0 allows attackers to read uninitialized process memory through a custom Read implementation. The Walue implementation for Vec sets a vector length beyond initialized bytes and passes that buffer to Read::read_exact. Exploitation requires a caller-controlled Read implementation; disclosed impact is limited to data already present in uninitialized process memory.
Summary
What happened
Memory exposure in the Rust postscript crate before 0.14.0 allows attackers to read uninitialized process memory through a custom Read implementation. The Walue implementation for Vec sets a vector length beyond initialized bytes and passes that buffer to Read::read_exact. Exploitation requires a caller-controlled Read implementation; disclosed impact is limited to data already present in uninitialized process memory.
The record
- CVE
- CVE-2021-26953
- Published
- Feb 9, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-908
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 9, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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