LiveActive security incident?Get immediate response
CVE Record

CVE-2022-35066: OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6e41b8.

OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6e41b8.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-35066 is a heap buffer overflow reported in OTFCC's otfccdump at commit 617837b. The main documented impact is availability loss, meaning a crafted input could crash processing. The supplied sources do not identify a fixed version, vendor advisory, or active exploitation.

Executive priority

Treat this as a moderate operational resilience issue. Prioritize teams that process externally supplied fonts or run automated font conversion pipelines. The business risk is service disruption, not confirmed breach risk, based on the supplied sources.

Technical view

The CVE describes CWE-787 out-of-bounds write behavior in /release-x64/otfccdump+0x6e41b8 for OTFCC commit 617837b. CVSS 3.1 is 6.5 with network attack vector, low complexity, no privileges, user interaction required, unchanged scope, and high availability impact only.

Likely exposure

Exposure is most likely where OTFCC or otfccdump is used to process fonts or related files, especially from untrusted sources. The source bundle lists no vendor, product CPE, package version range, or deployment context, so asset matching requires local inventory confirmation.

Exploitation context

The CVE is not listed as KEV in the supplied data. A public GitHub PoC reference is cited, but the bundle does not provide evidence of active exploitation. User interaction is required under the CVSS vector, and impact is documented as denial of service rather than data compromise.

Researcher notes

Evidence is thin: affected vendor/product fields are n/a, no CPEs are provided, and no fix is named. The strongest technical anchors are CWE-787, OTFCC commit 617837b, otfccdump offset detail, CVSS availability impact, and the public PoC reference.

Mitigation direction

  • Inventory OTFCC and otfccdump use across build, design, and processing systems.
  • Check upstream OTFCC guidance for fixed commits or replacement recommendations.
  • Avoid processing untrusted font files until exposure is understood.
  • Run font processing in sandboxed, resource-limited environments.
  • Remove or isolate vulnerable tooling where business need is low.

Validation and detection

  • Search SBOMs, repositories, images, and workstations for OTFCC or otfccdump.
  • Confirm whether any found build matches commit 617837b.
  • Identify workflows that accept external or user-supplied font files.
  • Review crash handling, sandboxing, and resource limits for affected processing paths.
  • Track vendor or upstream issue history for fixed-version evidence.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-2022-35066 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2022-35066Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-787 · source CWE mapping

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.