Security readout for executives and security teams
Plain-English summary
This CVE describes a crash in OTFCC's otfccdump component at commit 617837b. The business risk is denial of service when a vulnerable build processes a crafted input. The sources do not show data theft, data modification, named affected releases, or confirmed active exploitation.
Executive priority
Handle as a moderate availability risk. It does not currently justify emergency response based on the supplied evidence, but teams that automate OTFCC processing of external files should validate exposure and reduce crash impact promptly.
Technical view
The record maps the issue to CWE-787 and CVSS 3.1 score 6.5: network attack vector, low complexity, no privileges, user interaction required, unchanged scope, high availability impact only. The public description identifies a segmentation violation in /release-x64/otfccdump+0x6babea at commit 617837b.
Likely exposure
Exposure is most likely where OTFCC or derived otfccdump builds from commit 617837b process external or user-supplied files. The CVE data lists affected vendor, product, versions, and CPEs as n/a, so asset matching may require source or build provenance review.
Exploitation context
The bundle includes a public GitHub reference and Google Drive reference, but KEV is false and no cited source confirms active exploitation. CVSS indicates user interaction is required and impact is availability-only, so treat this as a crash risk rather than proven compromise.
Researcher notes
Evidence is sparse. The CVE names a commit and crash location but does not provide affected release ranges, CPEs, patch status, or exploitation-in-the-wild evidence. Validation should focus on whether local builds include the referenced commit or vulnerable code path.
Mitigation direction
- Identify any OTFCC or otfccdump deployments and record build provenance.
- Avoid processing untrusted inputs with affected builds until vendor guidance is reviewed.
- Check upstream OTFCC advisories or commits for a corrected build.
- Run vulnerable tooling in isolated, resource-limited environments where feasible.
- Prioritize replacement or removal if the tool is internet-facing in workflows.
Validation and detection
- Search software inventories for OTFCC and otfccdump binaries.
- Confirm whether any build traces to commit 617837b.
- Review processing workflows for external or user-submitted files.
- Check logs for repeated otfccdump crashes or abnormal terminations.
- Verify vendor or maintainer guidance before closing remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2022-35029 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://drive.google.com/file/d/1x0eGL9tYqc7BEapsTqD78FTu9H8GKZ6l/view?usp=sharingCVE reference · x_refsource_MISC
- https://github.com/Cvjark/Poc/blob/main/otfcc/CVE-2022-35029.mdCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.