otfccdump crash via crafted OpenType font
Published Aug 16, 2022 · Updated Aug 3, 2024
Heap-buffer overflow in OTFCC 0.10.4 allows context-dependent attackers to crash otfccdump via a crafted OpenType font file. Public records identify the failure only by the otfccdump release-x64 offset 0x6c0a32 and do not disclose the parser function or missing bounds check. A user must cause otfccdump to process the file; the published impact is a process crash, with no confidentiality or integrity impact.
Summary
What happened
Heap-buffer overflow in OTFCC 0.10.4 allows context-dependent attackers to crash otfccdump via a crafted OpenType font file. Public records identify the failure only by the otfccdump release-x64 offset 0x6c0a32 and do not disclose the parser function or missing bounds check. A user must cause otfccdump to process the file; the published impact is a process crash, with no confidentiality or integrity impact.
The record
- CVE
- CVE-2022-35461
- 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
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