Multiple Vendor xpdf StreamPredictor Heap Overflow Vulnerability
iDefense Security Advisory 12.05.05
December 5, 2005
Xpdf is an open-source viewer for Portable Document Format (PDF) files.
Local exploitation of a heap-based buffer overflow vulnerability in
xpdf, as included by various vendor's software distributions, could
allow attackers to cause a denial of service (DoS) condition,
potentially resulting in arbitrary code execution.
The vulnerability specifically exists due to insufficient input
validation in the Predictor stream parsing code. The
StreamPredictor::StreamPredictor function from xpdf/Stream.cc takes the
value of numComps from user-controllable data from within the PDF file.
The numComps value is used in a series of calcualations within the
StreamPredictor function. Using specially crafted values, a call to
gmalloc can be forced to allocate the minimum number of bytes, which
may later be overrun with user-supplied data from the PDF file leading
to corruption of heap memory that might result in a DoS condition or
arbitrary code execution.
Exploitation could result in arbitrary code execution with privileges
of the xpdf process. Currently, exploitation resulting in code
execution is theoretical and dependant on the process memory layout. A
typical exploitation attempt would require an attacker to supply a
malicious pdf to the victim. The victim would need to open the corrupt
pdf file in xpdf. Only then would the vulnerability be triggered.
iDefense has confirmed the existence of this vulnerability in xpdf
3.01. All earlier versions of xpdf are suspected vulnerable.
The following vendors include susceptible xpdf packages within their
operating system distributions:
. The Debian Project: Linux 3.0 and 3.1
iDefense is currently unaware of any effective workarounds for this
VI. VENDOR RESPONSE
A patch for this vulnerability is available at:
Updated binaries (version 3.01pl1) are available at:
VII. CVE INFORMATION
The Common Vulnerabilities and Exposures (CVE) project has assigned the
name CAN-2005-3192 to this issue. This is a candidate for inclusion in
the CVE list (http://cve.mitre.org), which standardizes names for
VIII. DISCLOSURE TIMELINE
10/13/2005 Initial vendor notification
10/19/2005 Initial vendor response
12/05/2005 Coordinated public disclosure
iDefense credits infamous41md (at) hotpop (dot) com [email concealed] with the discovery of this
Get paid for vulnerability research
Free tools, research and upcoming events
X. LEGAL NOTICES
Copyright C 2005 iDefense, Inc.
Permission is granted for the redistribution of this alert
electronically. It may not be edited in any way without the express
written consent of iDefense. If you wish to reprint the whole or any
part of this alert in any other medium other than electronically, please
email customerservice (at) iDefense (dot) com [email concealed] for permission.
Disclaimer: The information in the advisory is believed to be accurate
at the time of publishing based on currently available information. Use
of the information constitutes acceptance for use in an AS IS condition.
There are no warranties with regard to this information. Neither the
author nor the publisher accepts any liability for any direct, indirect,
or consequential loss or damage arising from use of, or reliance on,