Skip to content
Noroxi
CVE-2012-5669· NVD / CVE Program· CNA redhat

The _bdf_parse_glyphs function in FreeType before 2.4.11 allows context-dependent attackers to cause a denial of service (crash) and possibl

The _bdf_parse_glyphs function in FreeType before 2.4.11 allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via vectors related to BDF fonts and an incorrect calculation that triggers an out-of-bounds read.

MediumCVSS 4.3 · v2.0—No exploit Fix available
Published
Jan 24, 2013
Updated
Jun 16, 2026
EPSS
3.9% · 90th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
17 / 40 · 4.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.9%

Affected systems

VendorProduct
freetypefreetype

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • freetype freetypeup to 2.4.10 inclusive
  • freetype freetype1.3.1
  • freetype freetype2.0.0
  • freetype freetype2.0.1
  • freetype freetype2.0.2
  • freetype freetype2.0.3
  • freetype freetype2.0.4
  • freetype freetype2.0.5
  • freetype freetype2.0.6
  • freetype freetype2.0.7
  • freetype freetype2.0.8
  • freetype freetype2.0.9
  • freetype freetype2.1
  • freetype freetype2.1.10
  • freetype freetype2.1.3
  • freetype freetype2.1.4
  • freetype freetype2.1.5
  • freetype freetype2.1.6
  • freetype freetype2.1.7
  • freetype freetype2.1.8

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12freetypebefore 2.4.9-1.12.4.9-1.1
openSUSE:Tumbleweedft2demosbefore 2.7-1.12.7-1.1
Red Hat:enterprise_linux:5::serverfreetypebefore 0:2.2.1-32.el5_9.10:2.2.1-32.el5_9.1
Red Hat:enterprise_linux:5::serverfreetype-debuginfobefore 0:2.2.1-32.el5_9.10:2.2.1-32.el5_9.1
Red Hat:enterprise_linux:5::serverfreetype-demosbefore 0:2.2.1-32.el5_9.10:2.2.1-32.el5_9.1
Red Hat:enterprise_linux:5::serverfreetype-develbefore 0:2.2.1-32.el5_9.10:2.2.1-32.el5_9.1
Red Hat:enterprise_linux:6::clientfreetypebefore 0:2.3.11-14.el6_3.10:2.3.11-14.el6_3.1
Red Hat:enterprise_linux:6::clientfreetype-debuginfobefore 0:2.3.11-14.el6_3.10:2.3.11-14.el6_3.1
Red Hat:enterprise_linux:6::clientfreetype-demosbefore 0:2.3.11-14.el6_3.10:2.3.11-14.el6_3.1
Red Hat:enterprise_linux:6::clientfreetype-develbefore 0:2.3.11-14.el6_3.10:2.3.11-14.el6_3.1

Other highest-scoring records for the same primary product.

  • CVE-2025-27363An out of bounds write exists in FreeType versions 2.13.0 and below (newer versions of FreeType are not vulnerable) when attempting to parseKEV
    70This week
  • CVE-2012-1126FreeType before 2.4.9, as used in Mozilla Firefox Mobile before 10.0.4 and other products, allows remote attackers to cause a denial of serv
    42Plan
  • CVE-2022-27404FreeType commit 1e2eb65048f75c64b68708efed6ce904c31f3b2f was discovered to contain a heap buffer overflow via the function sfnt_init_face.
    40Plan
  • CVE-2015-9290In FreeType before 2.6.1, a buffer over-read occurs in type1/t1parse.c on function T1_Get_Private_Dict where there is no check that the new
    40Plan
  • CVE-2017-8287FreeType 2 before 2017-03-26 has an out-of-bounds write caused by a heap-based buffer overflow related to the t1_builder_close_contour funct
    40Plan
  • CVE-2017-8105FreeType 2 before 2017-03-24 has an out-of-bounds write caused by a heap-based buffer overflow related to the t1_decoder_parse_charstrings f
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:freetype2.4.9-1.1 · Debian:12Package registry (OSV)
opensuse:ft2demos2.7-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:freetype0:2.2.1-32.el5_9.1 · Red Hat:enterprise_linux:5::serverPackage registry (OSV)
red hat:freetype-debuginfo0:2.2.1-32.el5_9.1 · Red Hat:enterprise_linux:5::serverPackage registry (OSV)
red hat:freetype-demos0:2.2.1-32.el5_9.1 · Red Hat:enterprise_linux:5::serverPackage registry (OSV)
red hat:freetype-devel0:2.2.1-32.el5_9.1 · Red Hat:enterprise_linux:5::serverPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

    If successful

    Confidentiality
    none
    Integrity
    none
    Availability
    P · the service can be disrupted
    Attack complexity
    M
    Confidentiality impact
    None
    Integrity impact
    None
    Availability impact
    P

    CVSS vector

    AV:N/AC:M/Au:N/C:N/I:N/A:P

    nvd-primary

    Noroxi analysis

    No Noroxi analysis for this record yet

    We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

    We use this product, ask for help

    Change log

    1. Fix✗ → ✓

    For records you follow, these changes also arrive as notifications. →

    References

    All records