Local process crash via oversized stored-block copy
Published Jul 30, 2024 · Updated Aug 2, 2024
Heap buffer overflow in HiColor 0.5.0 allows local users to crash the command-line program by processing a crafted PNG file. In vendor/cute_png.h, cp_stored() passes an attacker-controlled stored-block length to memcpy, reading 65,280 bytes beyond a 43-byte heap allocation in the published sample. Exploitation requires invoking encode or quantize on the malicious image; the demonstrated consequence is process termination, not code execution.
Summary
What happened
Heap buffer overflow in HiColor 0.5.0 allows local users to crash the command-line program by processing a crafted PNG file. In vendor/cute_png.h, cp_stored() passes an attacker-controlled stored-block length to memcpy, reading 65,280 bytes beyond a 43-byte heap allocation in the published sample. Exploitation requires invoking encode or quantize on the malicious image; the demonstrated consequence is process termination, not code execution.
The record
- CVE
- CVE-2024-41438
- Published
- Jul 30, 2024
- Updated
- Aug 2, 2024
- Vendor
- dbohdan
- Product
- HiColor
- Classifications
- CWE-122
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 30, 2024CVE 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=0.5.0
What conditions does exploitation require?
What is affected?
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
- sample10.png 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