Crash via crafted OpenType font parsing
Published Sep 22, 2022 · Updated May 27, 2025
Memory corruption in otfccdump at OTFCC commit 617837b allows remote attackers to crash the utility with a crafted OpenType font. The public record identifies a segmentation fault at binary offset 0x6b6a8f but does not disclose the parser routine or invalid memory operation. A user must cause the file to be processed, and the documented consequence is termination of otfccdump without data disclosure or modification.
Summary
What happened
Memory corruption in otfccdump at OTFCC commit 617837b allows remote attackers to crash the utility with a crafted OpenType font. The public record identifies a segmentation fault at binary offset 0x6b6a8f but does not disclose the parser routine or invalid memory operation. A user must cause the file to be processed, and the documented consequence is termination of otfccdump without data disclosure or modification.
The record
- CVE
- CVE-2022-35032
- Published
- Sep 22, 2022
- Updated
- May 27, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119, T1499
- 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.
Weakness, pattern, technique
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