Memory corruption via unchecked buffer-size additions
Published Oct 19, 2023 · Updated Sep 12, 2024
Integer overflow in zchunk before 1.3.2 allows attackers to corrupt memory by supplying a malformed zchunk file. Four parsing and compression paths add attacker-controlled lengths to existing buffer sizes without first checking for size_t wraparound, then pass the wrapped totals to reallocation or header-reading operations. Processing of a crafted file is required; the resulting undersized buffers expose the consuming process to out-of-bounds memory access, although no public source establishes a specific exploit outcome.
Summary
What happened
Integer overflow in zchunk before 1.3.2 allows attackers to corrupt memory by supplying a malformed zchunk file. Four parsing and compression paths add attacker-controlled lengths to existing buffer sizes without first checking for size_t wraparound, then pass the wrapped totals to reallocation or header-reading operations. Processing of a crafted file is required; the resulting undersized buffers expose the consuming process to out-of-bounds memory access, although no public source establishes a specific exploit outcome.
The record
- CVE
- CVE-2023-46228
- Published
- Oct 19, 2023
- Updated
- Sep 12, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 19, 2023CVE publishedPublication date reported by the CVE source.
- Sep 12, 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