Skip to content
Fencer Intel
medium 6.8

CVE-2010-2807 json

FreeType before 2.4.2 uses incorrect integer data types during bounds checking, which allows remote attackers to cause a denial of service…

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

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

Summary

FreeType before 2.4.2 uses incorrect integer data types during bounds checking, which 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.2
  • apple iphone_os 4.2
  • apple mac_os_x 10.6.5
  • apple tvos 4.1.0
  • freetype Debian 14, Debian 13, Debian 12 2.4.2-1

debian advisories DEBIAN-CVE-2010-2807

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-2807 updated cvss 5.8

freetype: incorrect integer data types used during bounds checking

  • Red Hat Enterprise Linux 4 freetype Red Hat Enterprise Linux 5 freetype 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

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

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-681 Incorrect Conversion between Numeric Types

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.