LiveActive security incident?Get immediate response
CVE Record

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

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

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-35030 is a crash vulnerability in OTFCC's otfccdump component. The public record describes a segmentation violation in commit 617837b. Business impact is primarily availability: systems that automatically process untrusted font files could be disrupted. The source bundle does not identify packaged products, versions, or a vendor fix.

Executive priority

Handle as a moderate availability risk. Prioritize teams that process fonts from customers, partners, or the internet. The sparse vendor/version data lowers certainty, but automated font-processing services could face disruption if they run the affected code path.

Technical view

The CVE maps to CWE-787 and CVSS 3.1 score 6.5: network-accessible attack path, low complexity, no privileges, user interaction required, and high availability impact. The described failure is a segmentation violation in otfccdump at a specific release-x64 offset. Evidence is too sparse to infer code execution or confidentiality impact.

Likely exposure

Exposure is most likely where OTFCC or otfccdump processes externally supplied font files, especially in automated conversion, validation, upload, or CI workflows. The CVE data lists affected vendor, product, versions, and CPEs as n/a, so asset mapping requires local inventory.

Exploitation context

The bundle references a public PoC page, but KEV is false and no cited source confirms active exploitation. The CVSS vector requires user interaction, consistent with processing a crafted input rather than direct unauthenticated compromise. Treat exploitation evidence as limited to crash demonstration unless additional sources confirm more.

Researcher notes

The record is thin: affected product metadata is n/a, no fix is named, and the root cause is described only as a segmentation violation plus CWE-787. Do not assume RCE from the provided evidence. Focus research on reproducing crash conditions safely, version mapping, and upstream remediation status.

Mitigation direction

  • Identify and restrict OTFCC or otfccdump use on untrusted font files.
  • Check upstream OTFCC guidance for fixed commits, releases, or workarounds.
  • Run font processing in sandboxed, resource-limited workers.
  • Add queue isolation so parser crashes do not stop critical services.
  • Avoid internet-facing automated processing until exposure is confirmed.

Validation and detection

  • Inventory systems and pipelines invoking OTFCC or otfccdump.
  • Confirm whether they process user-supplied or third-party fonts.
  • Check deployed build provenance against commit 617837b and later upstream guidance.
  • Review crash logs for otfccdump segmentation faults during font handling.
  • Verify parser failures are contained and monitored.
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-35030 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-35030Attack 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.