Skip to content
Fencer Intel
medium 5.1

CVE-2010-2520 json

Heap-based buffer overflow in the Ins_IUP function in truetype/ttinterp.c in FreeType before 2.4.0, when TrueType bytecode support is enabl…

published 16y ago modified 4mo ago also EUVD-2010-2524

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

Summary

Heap-based buffer overflow in the Ins_IUP function in truetype/ttinterp.c in FreeType before 2.4.0, when TrueType bytecode support is enabled, 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-2520

Is CVE-2010-2520 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2520 updated cvss 7.5

freetype: heap buffer overflow vulnerability in truetype bytecode support

  • Red Hat All currently supported Red Hat products
    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.71% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

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

CVSS scores

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

Classification

Weakness

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.