LiveActive security incident?Get immediate response
CVE Record

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

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

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 tool when it processes a crafted input. Business impact is mainly availability: systems or workflows that automatically inspect untrusted fonts could fail or be disrupted. The sources do not identify a vendor advisory, fixed version, or broad product list.

Executive priority

Handle as a moderate availability issue. Prioritize if font processing is internet-facing, automated, or business-critical. Lower urgency is reasonable where OTFCC is absent or only used manually on trusted files.

Technical view

CVE-2022-35028 is reported against OTFCC commit 617837b as a segmentation violation in release-x64/otfccdump at offset 0x4fbbb6. It is classified as CWE-787 with CVSS 3.1 score 6.5, requiring user interaction and causing high availability impact without confidentiality or integrity impact.

Likely exposure

Exposure appears limited to environments using OTFCC otfccdump, especially automated font analysis or conversion pipelines handling untrusted files. The source bundle lists affected vendor, product, versions, and CPEs as n/a.

Exploitation context

The CVE references public proof-of-concept material, but the bundle does not cite CISA KEV listing or confirmed active exploitation. Treat it as a denial-of-service risk from malicious or malformed font input, not as proven real-world exploitation.

Researcher notes

Evidence is sparse: the record names a commit, binary offset, CWE-787, and CVSS vector, but not a vendor-maintained affected-version range or fix. Avoid extrapolating beyond OTFCC otfccdump and validate exposure from local asset evidence.

Mitigation direction

  • Inventory any use of OTFCC or otfccdump in build, upload, or analysis workflows.
  • Avoid processing untrusted fonts with affected OTFCC builds until vendor guidance is confirmed.
  • Isolate font-processing jobs with resource limits and failure containment.
  • Monitor the upstream OTFCC project and CVE record for fixed commits or releases.
  • Replace or disable exposed automated font parsing where business impact is low.

Validation and detection

  • Search repositories, containers, and build scripts for OTFCC and otfccdump usage.
  • Identify whether binaries map to commit 617837b or nearby unpatched builds.
  • Review upload and processing paths that accept user-supplied font files.
  • Confirm crash containment for font-processing workers and queues.
  • Track CVE and upstream references for authoritative remediation details.
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-35028 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-35028Attack 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.