Crash via malformed OpenType font parsing
Published Sep 19, 2022 · Updated Aug 3, 2024
Heap buffer overflow in OTFCC commit 617837b allows attackers to crash otfccdump by processing a crafted OpenType font. The disclosure locates the failure only at otfccdump offset 0x65fc97 and does not identify the faulty parser function or bounds operation. Execution requires a user or workflow to pass the file to the command-line utility; Debian reports no security impact where the affected code is not built.
Summary
What happened
Heap buffer overflow in OTFCC commit 617837b allows attackers to crash otfccdump by processing a crafted OpenType font. The disclosure locates the failure only at otfccdump offset 0x65fc97 and does not identify the faulty parser function or bounds operation. Execution requires a user or workflow to pass the file to the command-line utility; Debian reports no security impact where the affected code is not built.
The record
- CVE
- CVE-2022-35070
- Published
- Sep 19, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 19, 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.
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