LiveActive security incident?Get immediate response
CVE Record

CVE-2022-35032: OTFCC commit 617837b was discovered to contain a segmentation violation via /release-x64/otfccdump+0x6b6a8f.

OTFCC commit 617837b was discovered to contain a segmentation violation via /release-x64/otfccdump+0x6b6a8f.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-35032 is a crash vulnerability in OTFCC's otfccdump, reported against commit 617837b. A crafted input can trigger a segmentation violation, causing the tool or any dependent workflow to fail. The documented impact is availability loss only, not data theft or code execution.

Executive priority

Prioritize this if OTFCC supports customer-facing upload, conversion, or security-analysis workflows because exploitation could disrupt service availability. Treat it as lower urgency for isolated analyst workstations or trusted-only processing, but still track upstream remediation because affected version metadata is incomplete.

Technical view

The CVE describes a CWE-119 memory-safety issue in /release-x64/otfccdump at offset 0x6b6a8f. CVSS 3.1 is 6.5 with network attack vector, low complexity, no privileges, required user interaction, unchanged scope, and high availability impact. Source metadata does not identify precise affected product versions or a vendor fix.

Likely exposure

Exposure is most likely where OTFCC otfccdump from commit 617837b or related builds process untrusted font files, especially upload, conversion, analysis, or automated inspection pipelines. Exposure is lower where the tool is unused, isolated, or only handles trusted files.

Exploitation context

The bundle includes a public GitHub PoC reference, but CISA KEV status is false and no cited source states active exploitation. The CVSS vector requires user interaction, so practical abuse depends on getting a vulnerable workflow or user to process a malicious file.

Researcher notes

Evidence is sparse: affected vendor/product fields are n/a, and no patch is named in the bundle. The strongest facts are the vulnerable commit, otfccdump crash location, CWE-119 classification, CVSS availability impact, and public PoC reference. Avoid expanding scope beyond OTFCC without additional vendor confirmation.

Mitigation direction

  • Check OTFCC upstream guidance for fixed commits or releases.
  • Avoid processing untrusted font files with vulnerable otfccdump builds.
  • Run font parsing workflows in isolated, resource-limited environments.
  • Restrict customer or external font upload paths until validated.
  • Monitor crash logs for repeated otfccdump segmentation faults.

Validation and detection

  • Inventory systems, CI jobs, and services that invoke otfccdump.
  • Confirm whether deployed builds trace to commit 617837b.
  • Review upload and conversion paths for untrusted font processing.
  • Reproduce only in a controlled lab using non-production assets.
  • Do not run public PoC material against production systems.
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-119: 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-35032 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-35032Attack 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.