LiveActive security incident?Get immediate response
CVE Record

CVE-2022-35021: OTFCC commit 617837b was discovered to contain a global buffer overflow via /release-x64/otfccdump+0x718693.

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

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-35021 is a global buffer overflow reported in OTFCC’s otfccdump at commit 617837b. A crafted file processed by the tool could crash it, causing denial of service. The public record does not identify a vendor/product CPE, broad affected versions, or a named fixed release.

Executive priority

Treat as a targeted availability risk, not a confirmed enterprise-wide emergency. Prioritize review if the organization processes external fonts at scale or exposes font conversion services to customers, partners, or public uploads.

Technical view

The CVE describes CWE-120 in /release-x64/otfccdump+0x718693 with CVSS 3.1 score 6.5. The vector indicates network-reachable attack surface is possible, low complexity, no privileges, required user interaction, unchanged scope, and high availability impact only.

Likely exposure

Exposure is most likely where OTFCC or otfccdump processes untrusted font files, especially automated conversion, inspection, upload, or CI workflows. The source data lists affected vendor, product, versions, and CPEs as n/a, so asset matching requires local inventory.

Exploitation context

The bundle includes a public GitHub proof-of-concept reference, but no evidence of active exploitation. The CVE is not marked KEV. Successful impact appears limited to availability loss of the processing tool or dependent workflow, based on the provided CVSS fields.

Researcher notes

Evidence is sparse. The CVE record names an address in a release binary and a vulnerable commit, but does not provide CPEs, fixed versions, or vendor advisory details. Avoid over-scoping until local usage and upstream status are confirmed.

Mitigation direction

  • Check OTFCC upstream or maintainer guidance for fixed builds or recommended workarounds.
  • Avoid processing untrusted font files with affected otfccdump builds.
  • Run font-processing jobs in a sandboxed, least-privilege environment.
  • Limit automated font uploads or conversions until exposure is confirmed.
  • Add resource isolation around services that invoke otfccdump.

Validation and detection

  • Inventory systems, build scripts, containers, and services for OTFCC or otfccdump usage.
  • Compare local OTFCC builds against commit 617837b or related vulnerable builds.
  • Identify workflows that process user-supplied or third-party font files.
  • Confirm public APIs or upload paths do not directly trigger otfccdump processing.
  • Review crash, timeout, and availability monitoring for font-processing services.
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-120: 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-35021 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-35021Attack 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-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.