SUSE Linux Advisory: openssl

SUSE Security Announcement

Package: openssl
Announcement-ID: SuSE-SA:2004:007
Date: Wednesday, Mar 17th 2004 13:30 MEST
Affected products: 8.0, 8.1, 8.2, 9.0 SuSE Linux Database Server,
SuSE eMail Server III, 3.1 SuSE Linux Enterprise Server 7, 8 SuSE
Linux Firewall on CD/Admin host SuSE Linux Connectivity Server SuSE
Linux Office Server
Vulnerability Type: remote denial-of-service
Severity (1-10): 4
SUSE default package: yes
Cross References: CAN-2004-0079 CAN-2004-0112

Content of this advisory:

  1. security vulnerability resolved:
    • null pointer assignment due to handshake
    • crash with Kerberos cipher-suite support problem description,
      discussion, solution and upgrade information
  2. pending vulnerabilities, solutions, workarounds:
    • xf86_glx/xmodules/xloader
    • gnome-session
    • pwlib
    • libxml2
    • mod_python
    • mozilla
    • kernel
    • mailman
    • metamail
    • sysstat
  3. standard appendix (further information)

1) problem description, brief discussion, solution, upgrade

OpenSSL is an implementation of the Secure Socket Layer (SSL
v2/3) and Transport Layer Security (TLS v1) protocol. The NISCC
informed us about to failure conditions in openssl that can be
triggered to crash applications that use the openssl library.
The first bug occurs during SSL/TLS handshake in the function
do_change_cipher_spec() due to a NULL pointer assignment. The
second bug affects openssl version 0.9.7* only with Kerberos
cipher-suite enabled and can be triggered during SSL/TLS handshake

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.

There is not other solution known to this problem then updating
to the current version from our FTP servers.

To make this update effective, restart all servers using openssl

Intel i386 Platform:





patch rpm(s):




source rpm(s):







patch rpm(s):




source rpm(s):







patch rpm(s):




source rpm(s):







patch rpm(s):




source rpm(s):



2) Pending vulnerabilities in SUSE Distributions and

  • xf86_glx/xmodules/xloader
    The GLX and DRI code of the Xserver did not verify the “screen”
    parameter in several functions. This failure leads to a
    denial-ofservice condition and probably to arbitrary code execution
    as root. New packages are available on our FTP servers.
  • gnome-session
    This updates solves a problem with the initialization of the
    LD_LIBRARY_PATH while starting GNOME by using /usr/X11R6/bin/gnome.
    This bug can lead to local privilege escalation. New packages are
    available on our FTP servers.
  • pwlib
    This update addresses several security vulnerabilities that may be
    exploited remotely via applications that link with pwlib, like
    GnomeMeeting or alike. New packages are available on our FTP
  • libxml2
    A buffer overflow in the URI parsing code is fixed. This bug can
    lead to remote access to a system using libxml2. New packages are
    available on our FTP servers.
  • mod_python
    A remote denial-of-service attack can be triggered against the
    Apache web server by sending a specific query string that is
    processed by mod_python. New packages are available on our FTP
  • mozilla
    A buffer overflow in the S/MIME code of mozilla has been fixed
    which could allow remote attackers to execute arbitrary commands as
    the user running mozilla. Additionally a flaw in cookie handling
    (CAN-2003-0592) and a cross-site-scripting bug was fixed. In some
    cases (as with the mozilla package) the complexity of the issue
    does not allow to add patches any more. By consequence, security
    related issues in mozilla cannot be addressed. As a service to our
    user community, we provide packages of newer mozilla versions at
    These packages have been verified to run fine; they are not located
    in the update directory of the distribution in question because we
    cannot make any claims about the compatibility with the other
    packages in the product
  • kernel
    A new kernel release was made available. This update fixes some
    minor local denial-of-service attacks. Additionally, the 8.2
    versions also includes a missing patch from SuSE-SA:2004:005.
  • mailman
    A remote denial-of-service attack can be triggered in mailman 2.0.x
    (CAN-2003-0991). New packages will be available soon.
  • metamail
    This update fixes two buffer overflows and two format string bugs
    that can be exploited remotely in conjunction with other tools to
    gain access to a system with the privileges of the user running New
    packages will be available soon.
  • sysstat
    Two cases of insecure temporary file handling were found. The
    packages are currently being tested and will be available

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:

    1. md5sums as provided in the (cryptographically signed)
    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:


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



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


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


SUSE’s security contact is <security@suse.com> or

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>

Get the Free Newsletter!

Subscribe to Developer Insider for top news, trends, & analysis