LiveActive security incident?Get immediate response
CVE Record

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

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

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue can crash OTFCC's otfccdump when it processes a malicious or malformed font-related input. The documented impact is availability disruption, not data theft or tampering. Business urgency depends on whether OTFCC is used in exposed document, font, build, or content-processing workflows.

Executive priority

Prioritize if OTFCC is part of customer-facing upload, conversion, or automated content-processing paths. If usage is only local or trusted, handle through normal patch and hardening cycles.

Technical view

CVE-2022-35025 describes a segmentation violation in OTFCC commit 617837b at /release-x64/otfccdump+0x5266a8. It is mapped to CWE-787 and scored CVSS 3.1 6.5 with high availability impact, no confidentiality or integrity impact, and required user interaction.

Likely exposure

Exposure is most plausible where OTFCC or otfccdump processes fonts or submitted files from untrusted sources. The source bundle does not identify formal affected product versions, package names, CPEs, or downstream distributions.

Exploitation context

The bundle includes a public GitHub PoC reference, but KEV is false and no provided source states active exploitation. Treat exploit maturity as publicly documented crash reproduction, not confirmed real-world exploitation.

Researcher notes

The public record is sparse: affected vendor/product fields are n/a, and no patch details are supplied in the bundle. Analysis should remain scoped to OTFCC commit 617837b and otfccdump availability impact unless additional primary sources are obtained.

Mitigation direction

  • Inventory use of OTFCC and otfccdump in production and build workflows.
  • Avoid processing untrusted font files with affected builds.
  • Isolate font-processing jobs with resource limits and low privileges.
  • Check upstream or vendor guidance for fixed commits or releases.
  • Monitor crash telemetry for otfccdump segmentation faults.

Validation and detection

  • Confirm whether any deployed build traces to OTFCC commit 617837b.
  • Review pipelines that accept external fonts or documents containing fonts.
  • Check logs for repeated otfccdump crashes during file processing.
  • Verify remediation against upstream guidance before closing exposure.
  • Document any compensating isolation controls for vulnerable workflows.
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-35025 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-35025Attack 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.