LiveActive security incident?Get immediate response
CVE Record

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

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

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-35035 is a heap buffer overflow in OTFCC’s otfccdump component. If a vulnerable build processes a crafted font file, the main documented impact is service disruption or crash, not data theft. The public record does not identify a fixed version or affected product package.

Executive priority

Handle as a moderate availability risk. Prioritize if font processing supports customer-facing services, CI pipelines, or document ingestion. Deprioritize only after confirming OTFCC is absent or isolated from untrusted input.

Technical view

The CVE describes CWE-787 heap out-of-bounds memory access in OTFCC commit 617837b at an otfccdump offset. CVSS 3.1 is 6.5 with network attack vector, low complexity, no privileges, user interaction required, and high availability impact only.

Likely exposure

Exposure is most likely where OTFCC or otfccdump processes untrusted font files, especially upload, conversion, inspection, or build pipelines. The source bundle lists affected vendor, product, versions, and CPEs as n/a, so asset matching requires local software inventory.

Exploitation context

The CVE is not listed as KEV in the supplied bundle. A public GitHub proof-of-concept reference is cited, but the bundle provides no evidence of active exploitation in the wild. Treat exploit maturity as public but operational prevalence as unclear.

Researcher notes

The public CVE data is sparse: no vendor, package version, CPE, patch, or mitigation is identified. Analysis should focus on binary provenance, reachable input paths, and whether local builds match the referenced vulnerable commit.

Mitigation direction

  • Check OTFCC project guidance for a fixed commit or release.
  • Avoid processing untrusted fonts with vulnerable otfccdump builds.
  • Run font parsing in a sandboxed, resource-limited environment.
  • Remove otfccdump from internet-reachable upload or conversion paths.
  • Monitor crash reports tied to font parsing workflows.

Validation and detection

  • Inventory systems and pipelines using OTFCC or otfccdump.
  • Identify whether builds include or derive from commit 617837b.
  • Map font upload, conversion, and inspection routes to otfccdump usage.
  • Confirm untrusted files cannot reach vulnerable parsing paths.
  • Review logs for recurring otfccdump crashes or abnormal exits.
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-35035 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-35035Attack 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.