Process crash via heap buffer overflow
Published Oct 14, 2022 · Updated May 15, 2025
Heap buffer overflow in OTFCC otfccdump 0.10.4 and earlier allows remote attackers to crash it via a crafted font file. The public record identifies only the instrumented otfccdump offset 0x6b5567 and does not disclose the parser routine or unchecked operation. Exploitation requires a user to process attacker-supplied input; the reported consequence is a process crash without data disclosure or modification.
Summary
What happened
Heap buffer overflow in OTFCC otfccdump 0.10.4 and earlier allows remote attackers to crash it via a crafted font file. The public record identifies only the instrumented otfccdump offset 0x6b5567 and does not disclose the parser routine or unchecked operation. Exploitation requires a user to process attacker-supplied input; the reported consequence is a process crash without data disclosure or modification.
The record
- CVE
- CVE-2022-35040
- Published
- Oct 14, 2022
- Updated
- May 15, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 14, 2022CVE publishedPublication date reported by the CVE source.
- May 15, 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 CVE-2022-35040 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