Security readout for executives and security teams
Plain-English summary
CVE-2022-35068 is a heap buffer overflow reported in OTFCC at commit 617837b, specifically in otfccdump. The published scoring indicates the main business impact is denial of service, not data theft or tampering. The affected product and version metadata are incomplete, so exposure depends on whether your environment uses this exact tool or commit lineage.
Executive priority
Treat this as a moderate availability risk, not an emergency. Prioritize confirmation of whether OTFCC exists in your environment. If it is used on untrusted inputs or in automated pipelines, isolate or replace it pending upstream fix guidance.
Technical view
The CVE describes CWE-787 out-of-bounds write behavior in /release-x64/otfccdump at offset 0x6e420d. 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 record does not name fixed versions, affected package ranges, or vendor remediation.
Likely exposure
Likely limited to teams or build systems using OTFCC or otfccdump, especially around commit 617837b. The CVE record lists affected vendor, product, versions, and CPEs as n/a, so broad asset matching will be unreliable without local software inventory confirmation.
Exploitation context
The source bundle includes a public proof-of-concept reference, but CISA KEV is false and no cited source states active exploitation. The CVSS vector requires user interaction and indicates availability impact, suggesting crash or service disruption risk when vulnerable tooling processes attacker-influenced input.
Researcher notes
The record is sparse: affected vendor/product/version fields are n/a, and no fixed version is provided. Analysis confidence is constrained to the CVE description, CVSS vector, CWE classification, KEV status, and listed references. Avoid broad claims beyond OTFCC commit 617837b and otfccdump.
Mitigation direction
- Inventory any OTFCC or otfccdump use in development, CI, and content-processing workflows.
- Check upstream OTFCC project guidance for fixed commits or replacement builds.
- Avoid processing untrusted inputs with vulnerable otfccdump builds until vendor guidance is confirmed.
- Run vulnerable tooling in isolated, least-privileged environments where practical.
- Document any accepted risk if the tool is not present or not exposed to untrusted input.
Validation and detection
- Search software inventories and build images for OTFCC and otfccdump binaries.
- Confirm whether any installed build maps to commit 617837b or nearby source lineage.
- Review CI and automation for workflows that run otfccdump on external or user-supplied files.
- Check crash logs for otfccdump failures during input processing.
- Track vendor or upstream issue history for remediation details absent from the CVE record.
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-35068 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/193D7sPydmZiciaRD3r1UK_V3VT17GJFA/view?usp=sharingCVE reference · x_refsource_MISC
- https://github.com/Cvjark/Poc/blob/main/otfcc/CVE-2022-35068.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.