SuSE Linux Advisory: pine
Sep 11, 2003, 20:29 (0 Talkback[s])
WEBINAR: On-demand Event
Replace Oracle with the NoSQL Engagement Database: Why and how leading companies are making the switch REGISTER >
SuSE Security Announcement
||Thursday, Sep 11th 2003 08:40 MEST
||7.2, 7.3, 8.0, 8.1, 8.2
SuSE Linux Database Server, SuSE eMail Server III, 3.1 SuSE Linux
Enterprise Server 7, 8 SuSE Linux Firewall on CD/Admin host SuSE
Firewall on CD 2 SuSE Linux Connectivity Server SuSE Linux Office
Server SuSE Linux Desktop 1.0
||remote code execution
|SuSE default package:
Content of this advisory:
- security vulnerability resolved: An integer overflow and a
buffer overflow in the pine mail reader. problem description,
discussion, solution and upgrade information
- pending vulnerabilities, solutions, workarounds:
- standard appendix (further information)
- problem description, brief discussion, solution, upgrade
The well known and widely used mail client pine is vulnerable to
a buffer overflow. The vulnerability exists in the code processing
'message/external-body' type messages. It allows remote attackers
to execute arbitrary commands as the user running pine.
Additionally an integer overflow in the MIME header parsing code
has been fixed.
Since there is no workaround, an update is strongly recommended
for pine users.
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.
Intel i386 Platform:
PPC Power PC Platform:
2) Pending vulnerabilities in SuSE Distributions and
- gkrellmd The gkrellmd, part of the gkrellm package, contains a
buffer overflow. Only the gkrellm package shipped with SL 8.2 is
vulnerable. New update packages will be available on our FTP
- gdm2 The Gnome Display Manager (GDM) contains a bug which
allows local attackers to view any file on the system. Fixed
packages will be available on our FTP servers soon.
- kernel/PPC64 A locally exploitable vulnerability in the kernel
for SLES 8 PowerPC based IBM iSeries Systems allows an attacker to
overwrite arbitrary kernel memory. Update packages are being
published on our maintenance web, and our customers are being
- whois A buffer overflow exists in the whois command. New
packages will be available on our FTP servers soon.
- xfs The X font server (xfs) contains various integer overflows
which could allow remote attackers to execute arbitrary commands.
SuSE products do not enable xfs by default, but the update packages
should be installed as soon as they are available on our FTP
- postgresql The SQL database server postgresql of version 7.3.x
prior 7.3.4 is vulnerable to buffer overflow attacks. New packages
will be available soon.
3) standard appendix: authenticity verification, additional
- 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)
- 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 firstname.lastname@example.org), 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 "email@example.com"
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
For general information or the frequently asked questions (faq)
send mail to:
SuSE's security contact is <firstname.lastname@example.org
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.
||SuSE Security Team <email@example.com>
||SuSE Package Signing Key <firstname.lastname@example.org>