dbcve.org
Freetype Demo ProgramsApplication · Freedesktop

CVE-2022-31782

HIGH · 7.8 CVSS v3.1 Published 2022-06-02
Fix available
A fix is available. Upgrade to after 2.12.1 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
ftbench.c in FreeType Demo Programs through 2.12.1 has a heap-based buffer overflow.

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

A heap-based buffer overflow vulnerability exists in ftbench.c, a benchmark utility included in FreeType Demo Programs through version 2.12.1. The vulnerability allows an attacker to overwrite heap memory by providing specially crafted input to the ftbench tool, potentially leading to arbitrary code execution or denial of service.

MitigationUpdate FreeType Demo Programs to version 2.12.1 or later when patches become available. If using ftbench in production environments, remove or restrict access to demo programs until the fix is applied.

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
Freetype Demo ProgramsApplication
Affected:<= 2.12.1

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Locate the ftbench executable
    Search for the ftbench binary on the system using 'which ftbench' or 'find /usr -name ftbench 2>/dev/null'. Also check common bin directories like /usr/bin, /usr/local/bin, or installation directories used for FreeType demo programs.
    Affected if The ftbench executable is found on the system, indicating the FreeType Demo Programs are installed.
  2. Determine the FreeType Demo Programs version
    Run 'ftbench -v' or 'ftbench --version' if available. Alternatively, check the package manager for installed freetype-demo-packages using commands like 'dpkg -l | grep freetype' (Debian/Ubuntu) or 'rpm -qa | grep freetype' (RHEL/CentOS).
    Affected if The version returned is 2.12.1 or earlier, or the version cannot be determined but the demo programs are present.
  3. Verify the ftbench tool is accessible
    Check file permissions on the ftbench binary using 'ls -la' to see if it is executable by users. Confirm the binary exists in a location accessible to standard users.
    Affected if The ftbench binary is executable by users who could run it with malicious input.
  4. Identify if ftbench is in use or exposed
    Review any scripts, cron jobs, or applications that invoke ftbench. Check if ftbench is accessible via web-facing paths or shared directories where untrusted users could supply crafted input.
    Affected if ftbench is accessible to untrusted users or processes that could provide specially crafted input.

A user is affected if the FreeType Demo Programs (specifically ftbench) version 2.12.1 or earlier is installed and accessible to users who could run it with crafted input.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.12.1
Interim mitigation

Update FreeType Demo Programs to version 2.12.1 or later when patches become available. If using ftbench in production environments, remove or restrict access to demo programs until the fix is applied.

Recommended fix Moderate confidence

FreeType 2.12.2 or later stable release

  1. 1. Identify all systems running FreeType Demo Programs version 2.12.1 or earlier
  2. 2. Download the latest stable release of FreeType from the official repository or distribution package manager
  3. 3. Replace the vulnerable ftbench.c utility with the updated version from the new release
  4. 4. Rebuild and redeploy the demo programs if compiled from source
  5. 5. Verify the installation by checking the FreeType library version (freetype-config --version)
Caveat Minor - this is a security update for demo programs only; the core FreeType library should remain compatible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Freetype Demo Programs Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-31782 — 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-31782 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