LiveActive security incident?Get immediate response
CVE Record

CVE-2022-35036: OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6e1fc8.

OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6e1fc8.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-35036 is a heap buffer overflow reported in OTFCC commit 617837b, in otfccdump. The published CVSS score is medium, but availability impact is high. For executives, the main concern is service disruption where this tool processes untrusted input; the source bundle does not show data theft, integrity impact, or active exploitation.

Executive priority

Treat as a targeted availability risk, not a broad enterprise emergency. Prioritize asset discovery and containment where OTFCC is used in production or customer-facing file-processing workflows.

Technical view

The record describes CWE-787 in /release-x64/otfccdump+0x6e1fc8. CVSS 3.1 is 6.5 with network attack vector, low complexity, no privileges, required user interaction, unchanged scope, and high availability impact only. The affected product and version fields are not normalized beyond the named OTFCC commit.

Likely exposure

Exposure appears limited to environments running OTFCC otfccdump from or near commit 617837b, especially where users or automated workflows process untrusted files. The source bundle lists no CPEs, package versions, operating systems, or downstream distributions.

Exploitation context

The GitHub reference appears to be a public PoC-style disclosure, but the bundle does not support active exploitation. CVSS requires user interaction, so exploitation likely depends on a user or workflow processing crafted input with the vulnerable tool.

Researcher notes

Evidence is sparse. The CVE names a commit and crash location but lacks normalized affected versions, patch status, and vendor remediation. Analysis should avoid extrapolating beyond OTFCC otfccdump until upstream or distributor advisories confirm scope.

Mitigation direction

  • Check OTFCC upstream guidance for a fixed commit or release.
  • Avoid processing untrusted files with vulnerable otfccdump builds.
  • Run file-processing workflows in a sandboxed, least-privilege environment.
  • Disable automated ingestion paths until exposure is confirmed.
  • Monitor for abnormal crashes in workflows using otfccdump.

Validation and detection

  • Inventory systems and pipelines that invoke OTFCC or otfccdump.
  • Record exact source commit, package version, and build provenance.
  • Confirm whether commit 617837b or nearby code is deployed.
  • Review workflows for untrusted input reaching otfccdump.
  • Verify any vendor or upstream fix with non-offensive regression testing.
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-35036 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-35036Attack 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.