Process crash via oversized stdout buffer read
Published Mar 15, 2023 · Updated Feb 27, 2025
Heap-buffer over-read in jpegoptim 1.5.2 allows context-dependent attackers to crash the process via a crafted JPEG file. In optimize, stdin/stdout processing allocates a 65,536-byte input buffer, but the corrupt image makes fwrite read 88,156 bytes from that allocation. Exploitation requires the crafted file to be processed through stdin or with --stdout; the demonstrated consequence is an AddressSanitizer abort after an out-of-bounds read.
Summary
What happened
Heap-buffer over-read in jpegoptim 1.5.2 allows context-dependent attackers to crash the process via a crafted JPEG file. In optimize, stdin/stdout processing allocates a 65,536-byte input buffer, but the corrupt image makes fwrite read 88,156 bytes from that allocation. Exploitation requires the crafted file to be processed through stdin or with --stdout; the demonstrated consequence is an AddressSanitizer abort after an out-of-bounds read.
The record
- CVE
- CVE-2023-27781
- Published
- Mar 15, 2023
- Updated
- Feb 27, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 15, 2023CVE publishedPublication date reported by the CVE source.
- Feb 27, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- stdout-heapoverflow crafted JPEG 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