Process crash via unchecked chunk-name comparison
Published Oct 1, 2024 · Updated Mar 14, 2025
Heap buffer overflow in cute_png 1.05 allows context-dependent attackers to crash an application by supplying a crafted PNG file. The cp_chunk function performs a four-byte memcmp at the current input pointer without first ensuring that four bytes remain in the allocated PNG buffer. Exploitation requires an application using the library to process the file; the demonstrated consequence is an out-of-bounds read followed by process termination.
Summary
What happened
Heap buffer overflow in cute_png 1.05 allows context-dependent attackers to crash an application by supplying a crafted PNG file. The cp_chunk function performs a four-byte memcmp at the current input pointer without first ensuring that four bytes remain in the allocated PNG buffer. Exploitation requires an application using the library to process the file; the demonstrated consequence is an out-of-bounds read followed by process termination.
The record
- CVE
- CVE-2024-46276
- Published
- Oct 1, 2024
- Updated
- Mar 14, 2025
- Vendor
- Randy Gaul
- Product
- cute_png
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 1, 2024CVE publishedPublication date reported by the CVE source.
- Mar 14, 2025Record 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.05
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
- cp_chunk AddressSanitizer 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