CVE-2010-2519: Buffer Overflow
Heap-based buffer overflow in the MacReadPOSTResource function in base/ftobjs.c 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 length value in a POST fragment header in a font file.
Other sources
Robert Swiecki reported a heap buffer overflow vulnerability in freetype with how it processes certain fonts. 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 code is not present in Red Hat Enterprise Linux 3 (freetype 2.1.4).
This issue has been given the name CVE-2010-2519.
Upstream bug reports:
http://savannah.nongnu.org/bugs/index.php?30306
Upstream commits that fix the issue:
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=5ef20c8c1d4de12a84b50ba497c2a358c90ec44b http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=b2ea64bcc6c385a8e8318f9c759450a07df58b6d
Acknowledgements:
Red Hat would like to thank Robert Święcki of the Google Security Team for the discovery of this issue.
— Red Hat
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2010-2519?
CVE-2010-2519 is classified as a high severity vulnerability due to its potential to cause denial of service or arbitrary code execution.
How do I fix CVE-2010-2519?
To address CVE-2010-2519, update FreeType to version 2.4.0 or later, or apply relevant patches provided by your distribution.
What systems are affected by CVE-2010-2519?
CVE-2010-2519 affects FreeType versions prior to 2.4.0 and several versions of Ubuntu, Debian, and macOS.
What kind of attacks can exploit CVE-2010-2519?
CVE-2010-2519 can be exploited through crafted font files containing malicious POST fragment headers, leading to application crashes or code execution.
Is CVE-2010-2519 a zero-day vulnerability?
CVE-2010-2519 is not a zero-day vulnerability as it was publicly disclosed and addressed in updates to the affected software.