Security readout for executives and security teams
Plain-English summary
CVE-2022-35034 is a heap buffer overflow reported in OTFCC at commit 617837b, specifically involving otfccdump. The published CVSS score is 6.5, with availability impact rated high and no stated confidentiality or integrity impact. The sources do not identify affected releases, package names, or a vendor patch.
Executive priority
Treat this as a moderate operational risk. It is most important for teams that process external files with OTFCC tooling. Prioritize inventory and containment first because the public record lacks affected-version and patch details, while availability impact is explicitly high.
Technical view
The CVE describes CWE-787 out-of-bounds write behavior in OTFCC commit 617837b at an otfccdump code location. CVSS 3.1 indicates network attack vector, low complexity, no privileges required, user interaction required, unchanged scope, and availability-only impact. Public references include proof-of-concept material, but the bundle does not cite active exploitation.
Likely exposure
Exposure is likely limited to environments that use the referenced OTFCC or otfccdump build, or downstream builds containing the vulnerable code. Risk is higher where untrusted inputs are processed automatically. The source bundle does not provide CPEs, affected versions, operating systems, or distribution package names.
Exploitation context
The CVE is not listed as KEV in the provided bundle, so active exploitation is not established here. Public proof-of-concept references exist, which increases validation urgency, but the CVSS vector still requires user interaction and the documented impact is denial of service rather than data compromise.
Researcher notes
The record is sparse: affected vendor/product fields are n/a, and the description only names commit 617837b and an otfccdump offset. CVSS implies remote reachability with user interaction, but the bundle does not explain the full attack path. Public PoC references exist; avoid assuming active exploitation without KEV or other cited evidence.
Mitigation direction
- Inventory any OTFCC or otfccdump binaries in build, analysis, and intake workflows.
- Check upstream project guidance for fixed commits, replacement builds, or deprecation advice.
- Avoid processing untrusted inputs with affected otfccdump builds until remediated.
- Run file-processing workflows in isolated, resource-limited environments.
- Remove vulnerable binaries from automated intake paths where possible.
Validation and detection
- Confirm whether deployed OTFCC builds include commit 617837b or related code.
- Review package manifests, containers, and CI images for otfccdump usage.
- Map any user-supplied or external input paths reaching OTFCC tooling.
- Verify remediation against upstream guidance rather than assuming version safety.
- Check monitoring for crashes or repeated failures in otfccdump workflows.
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-35034 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/14qQpo_APymGhcKMU8B0epT20ImFC02LR/view?usp=sharingCVE reference · x_refsource_MISC
- https://github.com/Cvjark/Poc/blob/main/otfcc/CVE-2022-35034.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.