dbcve.org
OtfccApplication · Otfcc Project

CVE-2022-33047

CRITICAL · 9.8 CVSS v3.1 Published 2022-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

OTFCC v0.10.4 contains a heap buffer overflow after free (use-after-free) vulnerability in the otfccbuild.c component. This memory corruption issue allows an attacker to trigger the vulnerability during font processing, potentially leading to arbitrary code execution due to the critical CVSS score of 9.8.

MitigationUpdate to a patched version of OTFCC if available; otherwise upgrade to the latest stable release. If patching is not immediately feasible, restrict processing of untrusted font files and sanitize input to mitigate exploitation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OtfccApplication
Affected:= 0.10.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed OTFCC version
    Run 'otfccbuild -V' or check the binary version metadata using 'otfccdump --version' if available
    Affected if The version displayed is 0.10.4 exactly
  2. Locate otfccbuild binary
    Search for the otfccbuild executable in common paths like /usr/bin/, /usr/local/bin/, or via 'which otfccbuild'
    Affected if The otfccbuild binary exists and is version 0.10.4
  3. Verify otfccbuild.c compiled binary
    Check if otfccbuild has been compiled from source by inspecting the binary with 'file otfccbuild' or reviewing build documentation
    Affected if The binary was built from the v0.10.4 source release containing the vulnerable otfccbuild.c component
  4. Confirm font processing activity
    Review logs, cron jobs, or automation scripts that invoke otfccbuild to process font files
    Affected if OTFCC is actively used to build or process font files with the vulnerable version present

A user is affected if they are running OTFCC version 0.10.4 and using the otfccbuild component to process font files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of OTFCC if available; otherwise upgrade to the latest stable release. If patching is not immediately feasible, restrict processing of untrusted font files and sanitize input to mitigate exploitation.

Fix this in Otfcc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-33047 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-33047 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data