LiveActive security incident?Get immediate response
CVE Record

CVE-2022-33047: OTFCC v0.10.4 was discovered to contain a heap buffer overflow after free via otfccbuild.c.

OTFCC v0.10.4 was discovered to contain a heap buffer overflow after free via otfccbuild.c.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-33047 is a reported memory-safety flaw in OTFCC v0.10.4. The public record says it involves a heap buffer overflow after free in otfccbuild.c. The sources do not provide severity, business impact, affected platform details, or a confirmed fixed version.

Executive priority

Treat as a targeted inventory and containment item, not a confirmed emergency. Prioritize teams that process untrusted fonts or use OTFCC in automated pipelines. Escalate if upstream confirms remote code execution, active exploitation, or a fixed release.

Technical view

The CVE record describes a heap buffer overflow after free in OTFCC v0.10.4 via otfccbuild.c. No CVSS score, CWE, CPE, patch reference, or detailed attack vector is provided. Exposure analysis depends on whether OTFCC v0.10.4 or otfccbuild is present in build, font-processing, or developer tooling workflows.

Likely exposure

Organizations are likely exposed only if they use OTFCC v0.10.4, especially otfccbuild, in developer systems, CI pipelines, or font-processing workflows. The source bundle does not identify operating systems, package names, downstream products, or affected CPEs.

Exploitation context

CISA KEV is false in the provided data, and no cited source states active exploitation. The only external reference is a Google Drive URL; the bundle does not provide enough detail to confirm exploit maturity, prerequisites, or practical impact.

Researcher notes

Public metadata is sparse. The record names OTFCC v0.10.4 and otfccbuild.c but lacks CVSS, CWE, affected CPEs, and remediation details. Validate directly against upstream project artifacts before making exposure or exploitability claims.

Mitigation direction

  • Inventory systems and repositories for OTFCC v0.10.4 and otfccbuild usage.
  • Check upstream OTFCC guidance for patched versions or recommended workarounds.
  • Avoid processing untrusted font inputs with affected tooling until vendor guidance is confirmed.
  • Run necessary font-processing jobs in isolated, least-privileged environments.
  • Remove OTFCC where it is unused or no longer required.

Validation and detection

  • Confirm whether OTFCC v0.10.4 is installed in endpoints, servers, and CI images.
  • Review build scripts for otfccbuild invocation.
  • Identify workflows that process externally supplied fonts or font source files.
  • Check vendor or upstream release notes for CVE-2022-33047 references.
  • Document compensating controls if no confirmed patch is available.
Prepared
Confidence
medium
Sources
3

Public sources used

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.

cve · low confidence lookup

CVE-2022-33047 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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