Skip to content
Fencer Intel
medium 6.8

CVE-2010-2497 json

Integer underflow in glyph handling in FreeType before 2.4.0 allows remote attackers to cause a denial of service (application crash) or po…

published 2010-08-19 16 y ago modified 2026-06-16 4 mo ago also EUVD-2010-2501

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

Summary

Integer underflow in glyph handling in FreeType before 2.4.0 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted font file.

Patch / fix

  • freetype freetype 2.4.0
  • apple mac_os_x 10.6.5
  • freetype Debian 14, Debian 13, Debian 12 2.4.0-1

debian advisories DEBIAN-CVE-2010-2497

  • 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-2010-2497 updated cvss 7.5

freetype: integer underflow vulnerability

  • Red Hat Enterprise Linux 6 freetype, freetype-demos
    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

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

Exploits and checks

  • savannah.nongnu.org https://savannah.nongnu.org/bugs/?30082 referenced PoC, tagged "exploit" by a source, unverified
  • savannah.nongnu.org https://savannah.nongnu.org/bugs/?30083 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness
  • CWE-191 Integer Underflow (Wrap or Wraparound)

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.