Subject: iDEFENSE Security Advisory 01.18.05 - Multiple Unix/Linux Vendor Xpdf makeFileKey2 Stack Overflow
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
Date: Tue, 18 Jan 2005 16:38:57 -0500
Message-ID: <FB24803D1DF2A34FA59FC157B77C970503C8B298@idserv04.idef.com.>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: iDEFENSE Security Advisory 01.18.05 - Multiple Unix/Linux Vendor Xpdf makeFileKey2 Stack Overflow
Thread-Index: AcT9pi3Qi/wqCT8wRqCbnntQinWarQ==
From: "customer service mailbox" <customerservice@idefense.com.>
Sender: "Michael Sutton" <msutton@iDefense.com.>
To: <bugtraq@securityfocus.com.>, <vulnwatch@vulnwatch.org.>
X-Virus-Scanned: antivirus-gw at tyumen.ru
Multiple Unix/Linux Vendor Xpdf makeFileKey2 Stack Overflow=20
iDEFENSE Security Advisory 01.18.05
www.idefense.com/application/poi/display?id=3D186&type=3Dvulnerabilities
January 18, 2005
I. BACKGROUND
Xpdf is an open-source viewer for PDF files. More information is=20
available at the following site:
http://www.foolabs.com/xpdf/
II. DESCRIPTION
Remote exploitation of a buffer overflow vulnerability in the xpdf PDF=20
viewer included in multiple Unix and Linux distributions could allow for
arbitrary code execution as the user viewing a PDF file.=20
The vulnerability specifically exists due to insufficient bounds=20
checking while processing a PDF file that provides malicious values in=20
the /Encrypt /Length tag. The offending code can be found in the=20
Decrypt::makeFileKey2 function in the source file xpdf/Decrypt.cc.=20
GBool Decrypt::makeFileKey2(int encVersion, int encRevision,
int keyLength, GString *ownerKey,
GString *userKey, int permissions,
GString *fileID, String *userPassword,
Guchar *fileKey) {
Guchar *buf;
Guchar test[32];
Guchar fState[256];
Guchar tmpKey[16];
Guchar fx, fy;
int len, i, j;
GBool ok;
...
memcpy(test, userKey->getCString(), 32);
for (i =3D 19; i >=3D 0; --i) {
for (j =3D 0; j < keyLength; ++j) {
[overflow] tmpKey[j] =3D fileKey[j] ^ i;=20
}
...
}
...
}=20
In this piece of code, the keyLength value is ultimately supplied by the
PDF file. This allows an attacker to specify an arbitrarily large value=20
and overwrite portions of stack memory. As a consequence, arbitrary code
execution is possible.
III. ANALYSIS
Successful exploitation of this vulnerability leads to arbitrary code=20
execution as the user who opened the malicious file. An attacker would=20
have to convince a target to open the provided file in order to exploit=20
this vulnerability, thus lessening the impact.
Exploitation can be performed reliably, especially with knowledge of the
target system.
IV. DETECTION
iDEFENSE has confirmed the existence of this vulnerability in version=20
3.00 of xpdf. It is suspected previous versions are vulnerable.=20
The following Linux vendors may be affected by this vulnerability:
Novell Inc. (SUSE)=20
Red Hat Inc.=20
The Fedora Project=20
Debian Project=20
Gentoo Foundation Inc.=20
The FreeBSD Project=20
OpenBSD=20
V. WORKAROUND
Only open PDF files from trusted individuals.
VI. VENDOR RESPONSE
A patch to address this issue is available at:
ftp://ftp.foolabs.com/pub/xpdf/xpdf-3.00pl3.patch
Updated binaries (ver. 3.00pl3) to address this issue are available at:
http://www.foolabs.com/xpdf/download.html
VII. CVE INFORMATION
The Common Vulnerabilities and Exposures (CVE) project has assigned the
names CAN-2005-0064 to these issues. This is a candidate for inclusion
in the CVE list (http://cve.mitre.org), which standardizes names for
security problems.
VIII. DISCLOSURE TIMELINE
01/06/2005 Initial vendor notification
01/12/2005 Initial vendor response
01/18/2005 Coordinated public disclosure
IX. CREDIT
The discoverer of this vulnerability wishes to remain anonymous.
Get paid for vulnerability research
http://www.idefense.com/poi/teams/vcp.jsp
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 [email protected] 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,
this information.
