______________________________________________________________________________

                        SuSE Security Announcement

        Package:                openssl
        Announcement-ID:        SuSE-SA:2003:043
        Date:                   Wednesday, Oct 1st 2003 16:12 MET
        Affected products:      7.2, 7.3, 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):        5
        SuSE default package:   yes
        Cross References:       CAN-2003-0543
                                CAN-2003-0544
                                CAN-2003-0545

    Content of this advisory:
        1) security vulnerability resolved:
            - problems with ASN.1 encoding
            - accepting client certificates even if disabled
           problem description, discussion, solution and upgrade information
        2) pending vulnerabilities, solutions, workarounds:
            - whois
            - gdm2
            - postgresql
        3) standard appendix (further information)

______________________________________________________________________________

1)  problem description, brief discussion, solution, upgrade information

    OpenSSL is an implementation of the Secure Socket Layer (SSL v2/3)
    and Transport Layer Security (TLS v1) protocol.
    While checking the openssl implementation with a tool-kit from NISCC
    several errors were revealed most are ASN.1 encoding issues that
    causes a remote denial-of-service attack on the server side and
    possibly lead to remote command execution.

    There are two problems with ASN.1 encoding that can be triggered either
    by special ASN.1 encodings or by special ASN.1 tags.

    In debugging mode public key decoding errors can be ignored but
    also lead to a crash of the verify code if an invalid public key
    was received from the client.

    A mistake in the SSL/TLS protocol handling will make the server accept
    client certificates even if they are not requested. This bug makes
    it possible to exploit the bugs mentioned above even if client
    authentication is disabled.

    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 please.

    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.

    Please note that this update includes openssl, openssl-devel and
    openssl-doc.

    openssl:

    Intel i386 Platform:

    SuSE-9.0:
      
      88e30d20d288ecffe1e185b6ccc5099e
    patch rpm(s):
      
      68ffad90868b2107e3d82cc8fc50f6b7
    source rpm(s):
      
      1f5a12184b14ac5281f8da50da7deab6

    SuSE-8.2:
      
      20818d3b2d257bcf9258707e2adf8812
    patch rpm(s):
      
      2fbea6d1b3c19ed67d76337deef05363
    source rpm(s):
      
      24d40081aa2644a336279ecae878c1f3

    SuSE-8.1:
      
      a2c35048358d85fffd5a5ab7b58f6683
    patch rpm(s):
      
      08803c7ac279b8c9ad1dc4aef4146617
    source rpm(s):
      
      8bb653a4f779a125498f47dbaff0dc2f

    SuSE-8.0:
      
      671dc039955089f8523064272a4aad49
    patch rpm(s):
      
      4ae58f8e66b2cc7c2cc936132558ea46
    source rpm(s):
      
      7577ca638434ebe20406bfab85ec72ad

    SuSE-7.3:
      
      30ba99434b63d09d46cb271fac1bbefa
    source rpm(s):
      
      3485c804df9a381131462ba97697d6fb

    SuSE-7.2:
      
      d235ef6d8b990bfaadb974c205acdc40
    source rpm(s):
      
      5a753ed3919767077292f96728de3870



    Sparc Platform:

    SuSE-7.3:
      
      29caa7dd281c0891c8655bcd5367f1ca
    source rpm(s):
      
      6faf5fe6fa004eb5515c1777886c49c9



    PPC Power PC Platform:

    SuSE-7.3:
      
      b057f2204c43fdca13fcae041a45e977
    source rpm(s):
      
      7792ee3de5ef30c66c90a5fe43ee4eb2



    openssl-doc:

    Intel i386 Platform:

    SuSE-9.0:
      
      4a7d456b67a0456221cf69231270b4bd
    patch rpm(s):
      
      5223616e4b4d8f4bf0c02c63af75106c
    source rpm(s):
      
      1f5a12184b14ac5281f8da50da7deab6

    SuSE-8.2:
      
      fc79cc73f1a9ab5ddfd30cf6ddfb8ddc
    patch rpm(s):
      
      55c3f3afc117c1d3d49ea875057c8d72
    source rpm(s):
      
      24d40081aa2644a336279ecae878c1f3

    SuSE-8.1:
      
      0d094066c96a8880845e0775f9e60b73
    patch rpm(s):
      
      af8fcb4128569d603a018727eba8dc79
    source rpm(s):
      
      8bb653a4f779a125498f47dbaff0dc2f

    SuSE-8.0:
      
      c06870e5a8c6ea57471c13fb975c2c9f
    patch rpm(s):
      
      911c9fd73b10b9db32e60834a82a79ee
    source rpm(s):
      
      7577ca638434ebe20406bfab85ec72ad

    SuSE-7.3:
      
      119950dc0267c7038c21acf6d875afdd
    source rpm(s):
      
      3485c804df9a381131462ba97697d6fb

    SuSE-7.2:
      
      2f664c56f018c857f2f11f2e2634fbfa
    source rpm(s):
      
      5a753ed3919767077292f96728de3870



    Sparc Platform:

    SuSE-7.3:
      
      6cbb149f6a3fb62eb7cc71e817e80426
    source rpm(s):
      
      6faf5fe6fa004eb5515c1777886c49c9



    PPC Power PC Platform:

    SuSE-7.3:
      
      3f4235ab75c44e8e07c764ed2e4659da
    source rpm(s):
      
      7792ee3de5ef30c66c90a5fe43ee4eb2



    openssl-devel:

    Intel i386 Platform:

    SuSE-9.0:
      
      8cadccfaa0eeb50def65bdf1cfdba470
    patch rpm(s):
      
      c7349b7e87b828ee90d7e0b87b0f5d38
    source rpm(s):
      
      1f5a12184b14ac5281f8da50da7deab6

    SuSE-8.2:
      
      970728b4b4ae97d162a226a51a49c5b4
    patch rpm(s):
      
      f3cde2f53303041001edee7739dc4af1
    source rpm(s):
      
      24d40081aa2644a336279ecae878c1f3

    SuSE-8.1:
      
      b676506791a1d5ddbc97295443092e4b
    patch rpm(s):
      
      a9974f26f6a7280a71228b61b6a861cc
    source rpm(s):
      
      8bb653a4f779a125498f47dbaff0dc2f

    SuSE-8.0:
      
      6ecfb4d3546645282d62e65c3aec04ad
    patch rpm(s):
      
      1dbd101b9b7619de55d264191465b701
    source rpm(s):
      
      7577ca638434ebe20406bfab85ec72ad

    SuSE-7.3:
      
      0c2b11b0002d077219842e2b8e528af1
    source rpm(s):
      
      3485c804df9a381131462ba97697d6fb

    SuSE-7.2:
      
      4c206037061e780fdbc20254cfdc9e17
    source rpm(s):
      
      5a753ed3919767077292f96728de3870



    Sparc Platform:

    SuSE-7.3:
      
      40e0b55f40c1dfd110d3494240c2b533
    source rpm(s):
      
      6faf5fe6fa004eb5515c1777886c49c9



    PPC Power PC Platform:

    SuSE-7.3:
      
      f3a7e90f86c2c095ff3eae5d75a1a3c8
    source rpm(s):
      
      7792ee3de5ef30c66c90a5fe43ee4eb2


______________________________________________________________________________

2)  Pending vulnerabilities in SuSE Distributions and Workarounds:

    - gdm2
      Due to a bug in GDM it is possible for local users to read any text
      file on a system by creating a symlink from ~/.xsession-errors.
      New packages are available on our FTP servers.


    - whois
      The client tool whois is vulnerable to several buffer overflows
      while processing its command-line arguments. In conjunction with using
      untrusted data from remote sources as input, like using whois in a CGI
      script and so on, this buffer overflows may be abused to compromise
      a system.
      New packages are available on our FTP servers.

    - 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 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.

    1) execute the command
        md5sum 
       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.

    2) rpm package signatures provide an easy way to verify the authenticity
       of an rpm package. Use the command
        rpm -v --checksig 
       to verify the signature of the package, where  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:
        a) gpg is installed
        b) 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   .


  - 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>