LiveActive security incident?Get immediate response
CVE Record

CVE-2022-35064: OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x4adcdb i...

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

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This vulnerability is a heap buffer overflow in OTFCC's otfccdump tool. If someone is persuaded to process a malicious font file, the tool can crash, causing denial of service. The public record does not name specific packaged products, supported versions, or a fixed release.

Executive priority

Treat this as a targeted availability risk, not a broad internet-facing emergency. Prioritize teams that run automated font conversion, validation, or ingestion pipelines using OTFCC, especially where users or partners can submit font files.

Technical view

CVE-2022-35064 is reported against OTFCC commit 617837b, with a heap buffer overflow observed in otfccdump under ASan memset. It maps to CWE-787. CVSS 3.1 is 6.5 with user interaction required and high availability impact only.

Likely exposure

Exposure appears limited to systems where OTFCC/otfccdump from the referenced vulnerable code is used to process untrusted or externally supplied font files. The CVE record lists affected vendor, product, and versions as n/a, so asset matching requires local software inventory review.

Exploitation context

The source bundle references a public GitHub PoC page and a Google Drive artifact. CISA KEV status is false, and the provided sources do not state active exploitation in the wild.

Researcher notes

Evidence is thin: the CVE provides commit-level identification, crash location, CWE, CVSS, and external references, but no named vendor/product CPEs, fixed version, or maintainer advisory. Validate exposure by code lineage and operational use rather than CPE matching.

Mitigation direction

  • Identify any OTFCC or otfccdump usage in font-processing workflows.
  • Avoid processing untrusted font files with affected builds.
  • Run font parsing in a sandboxed, low-privilege environment.
  • Check the upstream project or package maintainer for fixed builds.
  • Prioritize replacement or isolation if no maintained fix is available.

Validation and detection

  • Search software inventories for OTFCC and otfccdump installations.
  • Confirm whether builds correspond to commit 617837b or vulnerable code.
  • Review services that accept or batch-process uploaded font files.
  • Check crash logs for otfccdump failures during font parsing.
  • Verify compensating controls around sandboxing and file-source restrictions.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-35064 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2022-35064Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.