LiveActive security incident?Get immediate response
CVE Record

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

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

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-35065 is an availability issue in OTFCC's otfccdump at commit 617837b. A crafted input can trigger a segmentation violation, causing the tool to crash. The main business risk is disruption where font processing is exposed to users or embedded in automated content pipelines.

Executive priority

Treat this as a moderate availability risk. Prioritize review if font processing is internet-facing, customer-driven, or part of critical publishing/build workflows. If OTFCC is not used, business exposure is likely low.

Technical view

The CVE describes a segmentation violation in /release-x64/otfccdump+0x65f724, classified as CWE-787. CVSS 3.1 is 6.5 with no confidentiality or integrity impact, but high availability impact. The record does not identify packaged affected versions, a fixed release, or vendor mitigation.

Likely exposure

Exposure is most likely in systems that use OTFCC or otfccdump to process font files, especially uploads or third-party font assets. The source bundle lists affected vendor, product, and versions as n/a, so asset confirmation requires local inventory.

Exploitation context

The CVSS vector requires user interaction and indicates network-reachable delivery is possible, but KEV status is false. The provided sources include a public proof-of-concept reference, yet do not establish active exploitation in the wild.

Researcher notes

Evidence is sparse: the CVE record names a specific commit and crash location, with CWE-787 and CVSS details, but no affected package versions or patch. Avoid assuming broader OTFCC versions are affected without reproducing against local builds or confirming upstream status.

Mitigation direction

  • Inventory OTFCC and otfccdump usage in build, upload, and asset-processing workflows.
  • Avoid processing untrusted font files without sandboxing and crash isolation.
  • Check upstream OTFCC guidance for a fixed commit, release, or recommended workaround.
  • Limit font upload paths to trusted users until exposure is understood.
  • Monitor font-processing services for repeated crashes or segmentation faults.

Validation and detection

  • Confirm whether any deployed build matches OTFCC commit 617837b.
  • Identify services or jobs that invoke otfccdump on user-supplied or third-party files.
  • Review crash logs for otfccdump segmentation violations during font processing.
  • Verify sandboxing, job timeouts, and service restart behavior around font-processing components.
  • Track upstream advisories because the CVE record does not name a fixed version.
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-35065 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-35065Attack 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.