Memory exposure via uninitialized parser buffer
Published Dec 26, 2021 · Updated Aug 4, 2024
Use of uninitialized memory in tectonic_xdv before 0.1.12 allows attackers controlling a Read implementation to expose process memory. XdvParser::::process allocates a 4,096-byte vector, unsafely sets its length without initializing the backing storage, and passes that buffer to the supplied Read implementation. Exploitation requires application code to invoke the parser with an attacker-controlled Read implementation; the resulting undefined behavior can disclose prior memory contents or crash the process.
Summary
What happened
Use of uninitialized memory in tectonic_xdv before 0.1.12 allows attackers controlling a Read implementation to expose process memory. XdvParser::::process allocates a 4,096-byte vector, unsafely sets its length without initializing the backing storage, and passes that buffer to the supplied Read implementation. Exploitation requires application code to invoke the parser with an attacker-controlled Read implementation; the resulting undefined behavior can disclose prior memory contents or crash the process.
The record
- CVE
- CVE-2021-45703
- Published
- Dec 26, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-908
- Attack vector
- network
- Privileges
- unauthenticated
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