Skip to content
Fencer Intel
medium 4.3

CVE-2012-5668 json

FreeType before 2.4.11 allows context-dependent attackers to cause a denial of service (NULL pointer dereference and crash) via vectors rel…

published 2013-01-24 13 y ago modified 2026-06-16 4 mo ago also EUVD-2012-5551

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.3%
EPSS 2.3% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

FreeType before 2.4.11 allows context-dependent attackers to cause a denial of service (NULL pointer dereference and crash) via vectors related to BDF fonts and the improper handling of an "allocation error" in the bdf_free_font function.

Patch / fix

  • freetype Debian 14, Debian 13, Debian 12 2.4.9-1.1

debian advisories DEBIAN-CVE-2012-5668

  • ft2demos openSUSE Tumbleweed 2.7-1.1
  • freetype2 openSUSE Tumbleweed 2.7-1.1

opensuse advisories openSUSE-SU-2024:10172-1openSUSE-SU-2024:10438-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-5668 updated cvss 4.3

freetype: NULL Pointer Dereference in bdf_free_font (#37905)

  • Red Hat Enterprise Linux 6 freetype, freetype-demos
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 5 freetype
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.34% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.