Skip to main content
VulnerabilityPublished Updated

CVE-2022-35064: OTFCC · Out-of-bounds Write

Source CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Sep 2022

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

To mitigate CVE-2022-35064, European organizations should: 1) Identify and inventory all instances of the OTFCC tool within their environments, including build and deployment pipelines. 2) Restrict the processing of font files from untrusted or unknown sources, implementing strict file validation and sandboxing where possible. 3) Monitor for updates or patches from the OTFCC project or related maintainers and apply them promptly once available. 4) Employ runtime protections such as AddressSanitizer or other memory safety tools during development and testing to detect similar issues early. 5) Implement network and endpoint security controls to prevent delivery of malicious font files, including email filtering and endpoint detection and response (EDR) solutions. 6) Educate users about the risks of opening untrusted font files and enforce policies limiting user interaction with such files. 7) Consider alternative font processing tools with a stronger security track record if OTFCC is critical but unpatched.

Description

OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x4adcdb in __asan_memset.

References

Community reviews

Loading reviews…