:SUSE Linux Advisory: xpdf, gpdf, kdegraphics3-pdf, pdftohtml, cups
SUSE Linux Advisory: xpdf, gpdf, kdegraphics3-pdf, pdftohtml, cups Oct 26, 2004, 18 :29 UTC (0 Talkback[s]) (2480 reads)
SUSE Security Announcement
Package: xpdf, gpdf, kdegraphics3-pdf, pdftohtml, cups
Announcement-ID: SUSE-SA:2004:039
Date: Tuesday, Oct 26th 2004 10:30 MEST
Affected products: 8.1, 8.2, 9.0, 9.1, 9.2
SUSE Linux Enterprise Server 8, 9
SUSE Linux Desktop 1.0
Vulnerability Type: remote system compromise
Severity (1-10): 5
SUSE default package: yes
Cross References: CAN-2004-0888
CAN-2004-0889
Content of this advisory:
security vulnerability resolved:
integer overflows
arithmetic errors
problem description
solution/workaround
special instructions and notes
package location and checksums
pending vulnerabilities, solutions, workarounds:
freeradius denial of service problems
mpg123
squid
standard appendix (further information)
1) problem description, brief discussion
Xpdf is a widely used fast PDF file viewer. Various other PDF viewer
and PDF conversion tools use xpdf code to accomplish their tasks.
Chris Evans found several integer overflows and arithmetic errors.
Additionally Sebastian Krahmer from the SuSE Security-Team found similar
bugs in xpdf 3.
These bugs can be exploited by tricking an user to open a malformated PDF
file. As a result the PDF viewer can be crashed or may be even code can be
executed.
2) solution/workaround
Due to the wide usage of xpdf-based code we do not recommend switching to
another PDF viewer as a workaround.
You have to install the updates.
3) special instructions and notes
Please restart all running instances of xpdf, gpdf, kpdf, pdftohtml, cups
after updating successfully.
4) package location and checksums
Please download the update package for your distribution and verify its
integrity by the methods listed in section 3) of this announcement.
Then, install the package using the command "rpm -Fhv file.rpm" to apply
the update.
Our maintenance customers are being notified individually. The packages
are being offered to install from the maintenance web.
Cups packages and all 9.2 packages will be available later.
5) pending vulnerabilities in SUSE Distributions and Workarounds:
freeradius
Several bugs that can be abused to remotely crash freeradius have
been discovered (CAN-2004-0938, CAN-2004-0960, CAN-2004-0961).
New packages will be available soon.
mpg123
A buffer overflow in mpg123 has been discovered. New packages will
be available soon.
squid
A bug in the ASN.1 parser of the SNMP module has been fixed which
would have allowed an attacker to crash squid (CAN-2004-0918).
Updates will be available soon.
6) standard appendix: authenticity verification, additional information
Package authenticity verification:
SUSE update packages are available on many mirror ftp servers all over
the world. While this service is being considered valuable and important
to the free and open source software community, many users wish to be
sure about the origin of the package and its content before installing
the package. There are two verification methods that can be used
independently from each other to prove the authenticity of a downloaded
file or rpm package:
md5sums as provided in the (cryptographically signed) announcement.
using the internal gpg signatures of the rpm package.
execute the command
md5sum <name-of-the-file.rpm>
after you downloaded the file from a SUSE ftp server or its mirrors.
Then, compare the resulting md5sum with the one that is listed in the
announcement. Since the announcement containing the checksums is
cryptographically signed (usually using the key security@suse.de),
the checksums show proof of the authenticity of the package.
We disrecommend to subscribe to security lists which cause the
email message containing the announcement to be modified so that
the signature does not match after transport through the mailing
list software.
Downsides: You must be able to verify the authenticity of the
announcement in the first place. If RPM packages are being rebuilt
and a new version of a package is published on the ftp server, all
md5 sums for the files are useless.
rpm package signatures provide an easy way to verify the authenticity
of an rpm package. Use the command
rpm -v --checksig <file.rpm>
to verify the signature of the package, where <file.rpm> is the
filename of the rpm package that you have downloaded. Of course,
package authenticity verification can only target an un-installed rpm
package file.
Prerequisites:
gpg is installed
The package is signed using a certain key. The public part of this
key must be installed by the gpg program in the directory
~/.gnupg/ under the user's home directory who performs the
signature verification (usually root). You can import the key
that is used by SUSE in rpm packages for SUSE Linux by saving
this announcement to a file ("announcement.txt") and
running the command (do "su -" to be root):
gpg --batch; gpg < announcement.txt | gpg --import
SUSE Linux distributions version 7.1 and thereafter install the
key "build@suse.de" upon installation or upgrade, provided that
the package gpg is installed. The file containing the public key
is placed at the top-level directory of the first CD (pubring.gpg)
and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de .
SUSE runs two security mailing lists to which any interested party may
subscribe:
The information in this advisory may be distributed or reproduced,
provided that the advisory is not modified in any way. In particular,
it is desired that the clear-text signature shows proof of the
authenticity of the text.
SUSE Linux AG makes no warranties of any kind whatsoever with respect
to the information contained in this security advisory.
Type Bits/KeyID Date User ID
pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team <security@suse.de>
pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build@suse.de>
