Security readout for executives and security teams
Plain-English summary
CVE-2022-35024 is a memory-safety crash issue reported in OTFCC commit 617837b. The documented impact is denial of service, not data theft or code execution. Business urgency is moderate unless OTFCC is used in automated workflows that process untrusted input.
Executive priority
Treat as a targeted availability risk. Escalate only if OTFCC processes externally supplied files in production or automated pipelines. Otherwise, handle through normal vulnerability management with inventory confirmation and vendor-guidance tracking.
Technical view
The CVE describes a CWE-119 segmentation violation in OTFCC commit 617837b, observed in memmove-vec-unaligned-erms.S. CVSS 3.1 is 6.5 with network attack vector, low complexity, no privileges, required user interaction, and high availability impact only. Affected product metadata is incomplete.
Likely exposure
Exposure is most likely limited to environments using OTFCC at or derived from commit 617837b. The CVE record lists vendor, product, versions, and CPEs as n/a, so asset matching will require software inventory review rather than CPE-based detection.
Exploitation context
The source bundle includes a public GitHub PoC reference, but CISA KEV is false and no provided source states active exploitation. The CVSS vector indicates user interaction is required. Evidence supports a crash or denial-of-service scenario, not confirmed compromise.
Researcher notes
The public record is sparse: affected vendor/product fields are n/a, and the description identifies a commit-level crash location. Do not assume broader OTFCC versions are affected without corroborating project evidence. Public PoC presence raises validation value but does not prove exploitation in the wild.
Mitigation direction
- Identify any OTFCC use in build, font, or conversion workflows.
- Check OTFCC project guidance for a fixed commit or release.
- Avoid processing untrusted files with affected OTFCC builds.
- Run conversion workloads in isolated, resource-limited environments.
- Prioritize replacement or removal if no maintained fix is available.
Validation and detection
- Search software inventories for OTFCC and commit 617837b-derived builds.
- Review CI, content-processing, and conversion pipelines for OTFCC execution.
- Confirm whether workflows accept files from external or untrusted sources.
- Map findings manually because the CVE has no usable CPE metadata.
- Document residual exposure if vendor remediation guidance is unavailable.
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-119: 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-35024 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/1s0VrWOJea_RRUJpZ0zgHV83NwGZlrIMt/view?usp=sharingCVE reference · x_refsource_MISC
- https://github.com/Cvjark/Poc/blob/main/otfcc/CVE-2022-35024.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.
Improper Restriction of Operations within the Bounds of a Memory Buffer
Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.