Security readout for executives and security teams
Plain-English summary
This CVE describes a crash in OTFCC's otfccdump at commit 617837b. The reported impact is service or tool availability, not data theft or modification. Business urgency is moderate where untrusted files are processed automatically or by users.
Executive priority
Prioritize if OTFCC is used in automated ingestion, customer-upload processing, or production workflows. Otherwise, handle through normal vulnerability management because the documented impact is availability-only and requires user interaction.
Technical view
The CVE reports a segmentation violation in /release-x64/otfccdump+0x4fbc0b and maps it to CWE-787. CVSS 3.1 is 6.5 with network attack vector, low complexity, no privileges, required user interaction, and high availability impact only.
Likely exposure
Exposure is most likely in environments that run OTFCC or otfccdump on untrusted inputs. The CVE data does not name packaged products, distributions, or affected version ranges beyond commit 617837b.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. Public references include PoC-related material, but the cited CVE evidence supports a crash or denial-of-service scenario, not confirmed real-world exploitation.
Researcher notes
Evidence is sparse: the CVE description repeats the crash location and does not provide affected version ranges or a named fix. Treat impact as denial of service unless additional vendor analysis proves broader memory-corruption consequences.
Mitigation direction
- Check upstream OTFCC guidance for fixed commits or releases.
- Avoid processing untrusted inputs with affected otfccdump builds.
- Run the tool in a constrained sandbox where practical.
- Limit automated processing paths that accept external files.
- Monitor vendor or project issue trackers for remediation details.
Validation and detection
- Inventory systems and pipelines using OTFCC or otfccdump.
- Check whether builds are based on commit 617837b.
- Review file-processing workflows for untrusted external inputs.
- Confirm whether sandboxing or job isolation is already enforced.
- Track remediation status against upstream project guidance.
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-35026 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/13A5FLmr3NiQZMNUpd9ir3owrnbn5lZbO/view?usp=sharingCVE reference · x_refsource_MISC
- https://github.com/Cvjark/Poc/blob/main/otfcc/CVE-2022-35026.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.