Process crash via undersized hdmx width allocation
Published Feb 20, 2024 · Updated Nov 3, 2025
Heap-based buffer overflow in TeX Live commit c515e allows remote attackers to crash ttfdump by supplying a crafted TTF file. ttfLoadHDMX allocates each Width buffer using the parsed hdmx size, then fread copies numGlyphs+1 bytes without verifying that the allocation is large enough. Processing the malicious font requires user interaction or an automated font-handling workflow; the confirmed consequence is a process crash.
Summary
What happened
Heap-based buffer overflow in TeX Live commit c515e allows remote attackers to crash ttfdump by supplying a crafted TTF file. ttfLoadHDMX allocates each Width buffer using the parsed hdmx size, then fread copies numGlyphs+1 bytes without verifying that the allocation is large enough. Processing the malicious font requires user interaction or an automated font-handling workflow; the confirmed consequence is a process crash.
The record
- CVE
- CVE-2024-25262
- Published
- Feb 20, 2024
- Updated
- Nov 3, 2025
- Vendor
- TeX Users Group
- Product
- TeX Live
- Classifications
- CWE-122, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 20, 2024CVE publishedPublication date reported by the CVE source.
- Nov 3, 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=c515e
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
No public exploit references are available in this record.
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