LiveActive security incident?Get immediate response
CVE Record

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

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

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE describes a heap buffer overflow in OTFCC’s otfccdump component at commit 617837b. A malicious or malformed input could crash the tool, causing availability impact. The provided sources do not identify broad product packaging, confirmed fixes, or active exploitation.

Executive priority

Handle as a moderate availability issue. Prioritize environments that automatically process external files, because service disruption is the main reported impact. This is not currently supported as an active exploitation emergency by the supplied sources.

Technical view

CVE-2022-35039 is reported as CWE-787 heap buffer overflow in OTFCC commit 617837b, associated with /release-x64/otfccdump+0x6e20a0. CVSS 3.1 is 6.5, with user interaction required and high availability impact, but no confidentiality or integrity impact reported.

Likely exposure

Exposure is most likely where OTFCC or otfccdump processes untrusted font or asset files, including developer workstations, automated asset pipelines, or backend conversion services. The CVE metadata lists affected vendor, product, versions, and CPEs as n/a, so scope must be confirmed locally.

Exploitation context

The bundle includes a public GitHub PoC reference, but the CVE is not marked KEV and no provided source states active exploitation. Treat this as a denial-of-service risk from crafted input rather than confirmed in-the-wild compromise evidence.

Researcher notes

The record is sparse: affected product fields are n/a, no patch is named, and the crash location is given without broader version mapping. Public PoC material exists, so validation should focus on inventory, input trust boundaries, and upstream commit history.

Mitigation direction

  • Check OTFCC upstream or vendor guidance for a fixed commit or release.
  • Avoid processing untrusted files with vulnerable otfccdump builds.
  • Run font-processing tools in isolated, least-privileged environments.
  • Remove unused OTFCC tooling from production and CI images.
  • Monitor CVE and upstream references for clarified affected versions.

Validation and detection

  • Inventory systems, containers, CI jobs, and developer tools for OTFCC or otfccdump.
  • Confirm whether any build maps to commit 617837b or nearby vulnerable code.
  • Identify workflows that process externally supplied font or asset files.
  • Review crash telemetry for otfccdump failures during file processing.
  • Track whether upstream has published a patched revision.
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-35039 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-35039Attack 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.