Process crash via heap-buffer overflow
Published Aug 16, 2022 · Updated Aug 3, 2024
Heap-buffer overflow in OTFCC otfccdump 0.10.4 allows context-dependent attackers to crash the process via a crafted OpenType font. The public disclosure identifies the fault only by otfccdump binary offset 0x6b0b2c and does not name the source function or unchecked field. Exploitation requires a user or application to process an attacker-supplied font, and the demonstrated consequence is process termination.
Summary
What happened
Heap-buffer overflow in OTFCC otfccdump 0.10.4 allows context-dependent attackers to crash the process via a crafted OpenType font. The public disclosure identifies the fault only by otfccdump binary offset 0x6b0b2c and does not name the source function or unchecked field. Exploitation requires a user or application to process an attacker-supplied font, and the demonstrated consequence is process termination.
The record
- CVE
- CVE-2022-35452
- Published
- Aug 16, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 16, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- OTFCC malformed-font sample and AddressSanitizer crash traceproof of concept · demonstrated
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