LiveActive security incident?Get immediate response
CVE Record

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

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

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-35022 is a crash vulnerability in OTFCC’s otfccdump component at commit 617837b. A crafted or problematic input can cause a segmentation violation, leading to denial of service. The public record does not name affected release versions or a confirmed fix.

Executive priority

Prioritize as moderate unless OTFCC processes external submissions in a business-critical path. The main business risk is service disruption, not confirmed data compromise, based on available evidence.

Technical view

The CVE describes a CWE-787 out-of-bounds write leading to a segmentation violation in /release-x64/otfccdump+0x6badae. CVSS 3.1 is 6.5 with no confidentiality or integrity impact and high availability impact. User interaction is required, and the source bundle does not confirm active exploitation.

Likely exposure

Exposure is most plausible where OTFCC or otfccdump processes untrusted font-related files, especially upload, conversion, analysis, or CI workflows. The affected product and version fields are listed as n/a, so inventory confirmation is necessary.

Exploitation context

The bundle includes a public proof-of-concept reference, but CISA KEV status is false and no cited source confirms active exploitation. Treat this as a denial-of-service risk rather than data theft based on the provided CVSS impacts.

Researcher notes

Evidence is sparse: the CVE gives a crash location, CWE-787, CVSS vector, and public PoC reference, but no affected release range, maintainer advisory, patch commit, or exploitation confirmation. Validation should focus on local usage and build provenance.

Mitigation direction

  • Inventory use of OTFCC and otfccdump across production, CI, and analyst workstations.
  • Avoid processing untrusted font files with builds from or near commit 617837b.
  • Sandbox or isolate font-processing jobs to limit crash impact.
  • Check upstream project guidance for fixed commits or release recommendations.
  • Add monitoring for repeated otfccdump crashes or failed font-processing jobs.

Validation and detection

  • Confirm whether any deployed OTFCC build maps to commit 617837b.
  • Review file-upload or conversion paths that pass user-supplied files into otfccdump.
  • Verify font-processing failures do not interrupt critical business workflows.
  • Track upstream advisories because affected versions and fixes are not named.
  • Document compensating controls if patch status cannot be confirmed.
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-35022 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-35022Attack 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.