Crash via heap out-of-bounds write
Published Sep 19, 2022 · Updated May 29, 2025
Heap buffer overflow in OTFCC otfccdump commit 617837b allows context-dependent attackers to crash the utility with a crafted font file. Public reports identify only binary offset 0x6c0bc3 and do not disclose the parser routine or unchecked operation that writes beyond the heap allocation. A victim must pass the malicious font to otfccdump for processing; the demonstrated consequence is a process crash, with no public evidence of code execution.
Summary
What happened
Heap buffer overflow in OTFCC otfccdump commit 617837b allows context-dependent attackers to crash the utility with a crafted font file. Public reports identify only binary offset 0x6c0bc3 and do not disclose the parser routine or unchecked operation that writes beyond the heap allocation. A victim must pass the malicious font to otfccdump for processing; the demonstrated consequence is a process crash, with no public evidence of code execution.
The record
- CVE
- CVE-2022-35062
- Published
- Sep 19, 2022
- Updated
- May 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 19, 2022CVE publishedPublication date reported by the CVE source.
- May 29, 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.
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
- Malformed-font proof-of-concept sampleproof of concept · unverified
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