Home Security

SUSE Linux Advisory: xpdf, gpdf, kdegraphics3-pdf, pdftohtml, cups

By

October 27, 2004

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.

x86 Platform:

SUSE Linux 9.0:

ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/pdftohtml-0.36-118.i586.rpm
dc822cef09e27e169acd94cda1fb622a

ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/xpdf-2.02pl1-141.i586.rpm
c99912bc5656546b028a8c4fe0473a75
patch rpm(s):

ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/pdftohtml-0.36-118.i586.patch.rpm
58b8a44ae02482d19c73959bfd85e85e

ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/xpdf-2.02pl1-141.i586.patch.rpm
8055fbed4ac1e664706701e3b7d3e1bc
source rpm(s):

ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/pdftohtml-0.36-118.src.rpm
35e37ded2db7d772d854748e606f42d0

ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/xpdf-2.02pl1-141.src.rpm
d42fe2976009b8ab44d6c166caf0840c

SUSE Linux 8.2:

ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/xpdf-2.01-137.i586.rpm
e198f2fc43f1f455676a9dc1ee42af5e
patch rpm(s):

ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/xpdf-2.01-137.i586.patch.rpm
acb5181c10c7b365cca71ae307b11553
source rpm(s):

ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/xpdf-2.01-137.src.rpm
aada3bee6ac1517f50468777c49d8d91

SUSE Linux 8.1:

ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/xpdf-1.01-255.i586.rpm
c0d7beba46d02e1090e9b6c7795a10c3
patch rpm(s):

ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/xpdf-1.01-255.i586.patch.rpm
ac395b4518a4c83d2af7805f35626a22
source rpm(s):

ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/xpdf-1.01-255.src.rpm
5ec84289ef8ca520e78cc80360d05665

x86-64 Platform:

SUSE Linux 9.0:

ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/pdftohtml-0.36-118.x86_64.rpm
942676168c21ac7253637dd3312e35d1

ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/xpdf-2.02pl1-141.x86_64.rpm
7a5076aec7aae7e6e05bf8d0f6b5e523
patch rpm(s):

ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/pdftohtml-0.36-118.x86_64.patch.rpm
b14da314a640e3afd3e72f417937c461

ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/xpdf-2.02pl1-141.x86_64.patch.rpm
fd4047d3c5392d63040e576effb32df5
source rpm(s):

ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/pdftohtml-0.36-118.src.rpm
5300f04533ee5b490e1f7de0a29fd705

ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/xpdf-2.02pl1-141.src.rpm
dd9b695199beaea8122037705eb1a581

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:
1. md5sums as provided in the (cryptographically signed)
  announcement.
2. using the internal gpg signatures of the rpm package.
3. 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.
4. 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:
  1. gpg is installed
  2. 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:

suse-security@suse.com
general/linux/SUSE security discussion. All SUSE security
announcements are sent to this list. To subscribe, send an email to

<suse-security-subscribe@suse.com>.

suse-security-announce@suse.com
SUSE’s announce-only mailing list.
Only SUSE’s security announcements are sent to this list. To
subscribe, send an email to

<suse-security-announce-subscribe@suse.com>.

For general information or the frequently asked questions (faq)
send mail to:

<suse-security-info@suse.com>
or
<suse-security-faq@suse.com>
respectively.

SUSE’s security contact is <security@suse.com> or
<security@suse.de>. The
<security@suse.de>
public key is listed below.

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>

Complete Story

Previous articleThe Salt Lake Tribune: SCO Stock Falls to Lowest Price Since It Filed IBM Suit

Next articleReuters: Red Hat Sees Half of Sales Outside U.S. in a Year

SUSE Linux Advisory: xpdf, gpdf, kdegraphics3-pdf, pdftohtml, cups

Get the Free Newsletter!

Must Read

How to Install Sails.js Framework on Ubuntu 22.04

How to Install Magento 2 on Ubuntu 24.04

GNOME 46.1 Desktop Environment Released with Explicit Sync Support

Linux Assistant: Tool to Help You Master Linux System Administration

How to Install WordPress on Ubuntu 24.04

Our Brands