LiveActive security incident?Get immediate response
CVE Record

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

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

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE describes a crash in OTFCC's otfccdump when processing a crafted input. The documented impact is denial of service, not data theft or integrity compromise. Business urgency is moderate and depends on whether OTFCC processes fonts or related files from untrusted sources.

Executive priority

Treat this as a moderate availability risk. Prioritize remediation where font processing is internet-facing, automated, or business-critical. Lower urgency is reasonable for isolated researcher workstations with trusted inputs and sandboxing.

Technical view

CVE-2022-35031 is reported against OTFCC commit 617837b, with a segmentation violation in otfccdump. The CVE maps it to CWE-787 and CVSS 3.1 score 6.5, with high availability impact and no confidentiality or integrity impact. Exact affected product and version metadata is not provided.

Likely exposure

Exposure is most plausible where OTFCC or otfccdump is used in automated font processing, CI pipelines, content ingestion, or researcher tooling that handles external files. The source bundle does not identify packaged product versions or CPEs.

Exploitation context

The CVSS vector requires user interaction and indicates a low-complexity, unauthenticated path to availability impact. KEV is false, and the provided sources do not state active exploitation. A public proof-of-concept reference is listed, but exploitation details should not be operationalized.

Researcher notes

The evidence is sparse: affected vendor, product, versions, and CPEs are marked n/a. The strongest source-grounded facts are the commit reference, otfccdump crash location, CWE-787 classification, CVSS vector, and non-KEV status.

Mitigation direction

  • Check OTFCC project guidance for fixed commits, releases, or maintainer recommendations.
  • Avoid processing untrusted font files with vulnerable otfccdump builds.
  • Run OTFCC tooling in a sandboxed, resource-limited environment.
  • Restrict automated ingestion paths that pass external files into otfccdump.
  • Monitor dependency inventories for OTFCC commit or package usage.

Validation and detection

  • Inventory systems, build scripts, and containers for OTFCC or otfccdump usage.
  • Map deployed builds to commit 617837b or nearby vulnerable code history.
  • Review workflows that accept external or user-supplied font files.
  • Confirm whether crashes affect production services or only isolated tooling.
  • Document compensating controls if no upstream fix is identified.
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-35031 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-35031Attack 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.