Process crash via out-of-bounds quantization write
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 png_quantize() at cli.c line 220, a one-byte write crosses the boundary of a heap buffer returned by rgb_to_cp while quantizing the malicious image. The crafted file must be processed by the local quantize command; the demonstrated consequence is process termination, with no sourced confidentiality or integrity impact.
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 png_quantize() at cli.c line 220, a one-byte write crosses the boundary of a heap buffer returned by rgb_to_cp while quantizing the malicious image. The crafted file must be processed by the local quantize command; the demonstrated consequence is process termination, with no sourced confidentiality or integrity impact.
The record
- CVE
- CVE-2024-41440
- Published
- Jul 30, 2024
- Updated
- Aug 2, 2024
- Vendor
- dbohdan
- Product
- HiColor
- Classifications
- CWE-122, T1204.002
- 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.
Public exploit references
- sample18.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