Process crash via crafted OpenType font
Published Sep 19, 2022 · Updated May 29, 2025
Out-of-bounds write in OTFCC commit 617837b allows attackers to crash otfccdump by supplying a crafted OpenType font file. Public records identify the failing otfccdump offset and weakness class but do not disclose the parser routine or unchecked write. Execution requires otfccdump to process the file, and the documented consequence is a process crash without confidentiality or integrity impact.
Summary
What happened
Out-of-bounds write in OTFCC commit 617837b allows attackers to crash otfccdump by supplying a crafted OpenType font file. Public records identify the failing otfccdump offset and weakness class but do not disclose the parser routine or unchecked write. Execution requires otfccdump to process the file, and the documented consequence is a process crash without confidentiality or integrity impact.
The record
- CVE
- CVE-2022-35065
- 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
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