Crash via unchecked voxel-coordinate indexing
Published Feb 24, 2023 · Updated Aug 2, 2024
Heap-based buffer overflow in jemisa vox2png 1.0 allows attackers to crash the converter by supplying a crafted .vox file. In main, voxel coordinates from the file are combined into dataIndex and used to write currentColor into pngData without bounds checking. A user must run the local command-line tool on the file; the demonstrated result is an out-of-bounds heap access followed by a segmentation fault or AddressSanitizer abort.
Summary
What happened
Heap-based buffer overflow in jemisa vox2png 1.0 allows attackers to crash the converter by supplying a crafted .vox file. In main, voxel coordinates from the file are combined into dataIndex and used to write currentColor into pngData without bounds checking. A user must run the local command-line tool on the file; the demonstrated result is an out-of-bounds heap access followed by a segmentation fault or AddressSanitizer abort.
The record
- CVE
- CVE-2023-1010
- Published
- Feb 24, 2023
- Updated
- Aug 2, 2024
- Vendor
- jemisa
- Product
- vox2png
- Classifications
- CWE-122, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 24, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0
What conditions does exploitation require?
What is affected?
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.
Public exploit references
- id11 crafted .vox proof of conceptproof of concept · demonstrated
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