Red Hat Bugzilla – Bug 613198
CVE-2010-2520 freetype: heap buffer overflow vulnerability in truetype bytecode support
Last modified: 2015-08-19 04:49:58 EDT
Robert Swiecki reported a heap buffer overflow vulnerability in freetype's truetype bytecode support. This could cause applications linked against freetype to crash or, possibly, lead to the execution of arbitrary code if an attacker were able to get a victim to load a malicious font file.
The affected functionality (truetype bytecode) is not compiled in Red Hat Enterprise Linux or Fedora by default.
This issue has been given the name CVE-2010-2520.
Upstream bug reports:
Upstream commit that fixes the issue:
Not vulnerable. This issue did not affect the versions of freetype as shipped with Red Hat Enterprise Linux 3, 4, or 5.
Provided we never enable truetype bytecode support (doubtful since it's patented) this won't affect any version of freetype we ship.
Users that have rebuilt freetype with truetype bytecode support enabled will probably want to patch this and rebuild again to get the fix, or revert to the (supported) version of freetype as provided (with truetype bytecode support disabled).
Is there a Freetype security update in the works for the other CVEs or should I patch freetype-freeworld for just this CVE while waiting on a decision for the others?
Referring to Fedora updates? I'm not sure. There is no new upstream version as of yet (probably sometime next week). I was going to create a tracking bug for all of these flaws (well, excluding this one -- you can certainly include the patch for it if you like). I'll do that in a minute.
Actually, I'm going to open this so that we can get the fixes into Fedora.
(In reply to comment #1)
> Provided we never enable truetype bytecode support (doubtful since it's
> patented) this won't affect any version of freetype we ship.
The patents have expired and it was enabled (briefly) in Fedora
It's disabled again for non-legal reasons (enabling it disables the autohinter, we'd like it to be enabled for glyphs with hints, and autohint the rest)
Therefore, it would be a good idea to fix it preventively before it is enabled again
Upstream has released 2.4.0 to correct this issue: