Utility crash via out-of-bounds parser write
Published Sep 22, 2022 · Updated May 27, 2025
Out-of-bounds write in OTFCC otfccdump commit 617837b allows attackers to crash the utility via a crafted font file. Public records identify the failing locus only as otfccdump offset 0x4fbc0b and do not disclose the parser routine or unchecked field that causes the invalid write. Exploitation requires a user to process the file; the published impact is limited to termination of the otfccdump process, with no disclosed data access or code execution.
Summary
What happened
Out-of-bounds write in OTFCC otfccdump commit 617837b allows attackers to crash the utility via a crafted font file. Public records identify the failing locus only as otfccdump offset 0x4fbc0b and do not disclose the parser routine or unchecked field that causes the invalid write. Exploitation requires a user to process the file; the published impact is limited to termination of the otfccdump process, with no disclosed data access or code execution.
The record
- CVE
- CVE-2022-35026
- Published
- Sep 22, 2022
- Updated
- May 27, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 22, 2022CVE publishedPublication date reported by the CVE source.
- May 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.
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
- Cvjark OTFCC crash proof of conceptproof 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