Process crash via out-of-bounds font read
Published Aug 16, 2022 · Updated Aug 3, 2024
Out-of-bounds read in OTFCC 0.10.4 allows attackers to crash otfccdump by supplying a crafted OpenType font for processing. The public report identifies a segmentation violation at otfccdump offset 0x4fbbb6 but does not disclose the faulty source operation. A user or consuming workflow must pass attacker-controlled font input to the command-line parser; the documented consequence is a process crash only.
Summary
What happened
Out-of-bounds read in OTFCC 0.10.4 allows attackers to crash otfccdump by supplying a crafted OpenType font for processing. The public report identifies a segmentation violation at otfccdump offset 0x4fbbb6 but does not disclose the faulty source operation. A user or consuming workflow must pass attacker-controlled font input to the command-line parser; the documented consequence is a process crash only.
The record
- CVE
- CVE-2022-35479
- Published
- Aug 16, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, 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
- Cvjark OTFCC crash 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