First published: Thu Sep 30 2010(Updated: )
An array indexing error was found in the way xpdf / poppler parsed Type1 fonts embedded in PDF documents. In FoFiType1::parse(), text representation of the numeric code value was converted to integer value using atoi(). This value was checked to ensure it's less than 256, but there was no check to ensure it's not negative (string passed to atoi() was checked to only contain characters '0'-'9' before the call though). On platforms, where atoi() could return negative result when parsing large positive values (exceeding INT_MAX), this could could lead to write out of array bounds due to use of negative index. poppler upstream commit: <a href="http://cgit.freedesktop.org/poppler/poppler/commit/?id=39d140bfc0b8239bdd96d6a55842034ae5c05473">http://cgit.freedesktop.org/poppler/poppler/commit/?id=39d140bfc0b8239bdd96d6a55842034ae5c05473</a> Reference: <a href="http://secunia.com/advisories/41596/">http://secunia.com/advisories/41596/</a>
Affected Software | Affected Version | How to fix |
---|---|---|
Poppler Data |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-638960 is rated as a critical vulnerability due to potential exploitation risks.
To fix REDHAT-BUG-638960, update to the latest version of Poppler that addresses this vulnerability.
The potential impacts of REDHAT-BUG-638960 include arbitrary code execution or denial of service when processing specially crafted PDF files.
Your system may be affected by REDHAT-BUG-638960 if you are using vulnerable versions of Poppler that process Type1 fonts in PDF documents.
REDHAT-BUG-638960 was reported on Red Hat's Bugzilla, indicating an urgent need for resolution due to its nature.