LiveActive security incident?Get immediate response
CVE Record

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

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

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-35027 is a crash bug in OTFCC's otfccdump component at commit 617837b. The documented impact is availability loss: a user or workflow must process a problematic input, causing a segmentation violation. The sources do not identify a vendor advisory, fixed version, or broader product list.

Executive priority

Treat this as a moderate availability risk, not a confirmed data compromise issue. Prioritize teams that process external or customer-supplied files with OTFCC, because the available evidence points to crash impact and incomplete remediation detail.

Technical view

The record describes a segmentation violation in /release-x64/otfccdump+0x4fe9a7 and maps it to CWE-787. CVSS 3.1 is 6.5: network attack vector, low complexity, no privileges, user interaction required, unchanged scope, no confidentiality or integrity impact, high availability impact.

Likely exposure

Exposure appears limited to environments using OTFCC otfccdump from or near commit 617837b, especially where untrusted files are inspected by users or automation. The CVE record lists affected vendor, product, versions, and CPEs as n/a, so precise exposure cannot be confirmed from the provided sources.

Exploitation context

The bundle includes a public GitHub PoC reference, but no KEV listing and no cited evidence of active exploitation. The CVSS vector requires user interaction, so practical risk depends on whether vulnerable otfccdump is reachable through user workflows or automated processing.

Researcher notes

Evidence is sparse: affected product metadata is n/a, and the description names only a commit and crash offset. Do not infer remote service exposure without local deployment context. The PoC reference supports reproducibility, but not active exploitation.

Mitigation direction

  • Check upstream OTFCC guidance for a fixed commit or release.
  • Avoid processing untrusted files with affected otfccdump builds.
  • Run parsing workflows in a restricted, disposable environment.
  • Limit automated ingestion paths that invoke otfccdump.
  • Track vendor or maintainer advisories for remediation details.

Validation and detection

  • Inventory systems and pipelines that use OTFCC or otfccdump.
  • Confirm whether deployed builds match commit 617837b or related vulnerable code.
  • Review crash reports for otfccdump segmentation faults.
  • Verify whether untrusted inputs can reach otfccdump workflows.
  • Document any compensating sandboxing or isolation controls.
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-35027 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-35027Attack 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.