______________________________________________________________________________

                        SuSE Security Announcement

        Package:                mysql
        Announcement-ID:        SuSE-SA:2003:042
        Date:                   Wed Oct  1 12:12:38 CEST 2003
        Affected products:      7.2, 7.3, 8.0, 8.1, 8.2
                                SuSE Linux Connectivity Server
                                SuSE Linux Enterprise Server 7, 8
                                SuSE Linux Office Server
                                UnitedLinux 1.0
        Vulnerability Type:     remote code execution
        Severity (1-10):        5
        SuSE default package:   no
        Cross References:       -

    Content of this advisory:
        1) security vulnerability resolved: Buffer overflow in mysql.
           problem description, discussion, solution and upgrade information
        2) pending vulnerabilities, solutions, workarounds:
            - OpenSSL
        3) standard appendix (further information)

______________________________________________________________________________

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

    A remotely exploitable buffer overflow within the authentication code
    of MySQL has been reported. This allows remote attackers who have
    access to the 'User' table to execute arbitrary commands as mysql user.
      The list of affected packages is as follows:
    mysql, mysql-client, mysql-shared, mysql-bench, mysql-devel, mysql-Max.
    In this advisory the MD5 sums for the mysql, mysql-shared and mysql-devel
    packages are listed.

    To be sure the update takes effect you have to restart the MySQL server
    by executing the following command as root:

        /usr/sbin/rcmysql restart

    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.

    i386 Intel Platform:

    SuSE-8.2:
      
      41e8d3781aeedd2e48837293d261f9e2
      
      b75bdea7f484305c62415cd7412151af
      
      264920dc6e1def4e26253cc3d82f2fc7
    patch rpm(s):
      
      82bac86826eb08ccf8c3204a792e0df1
      
      ea14dd33b2e390009513209e71229cd3
      
      b8e64deab45bdd05657a5447b4e279eb
    source rpm(s):
      
      fd33faf5fe7efc9f9c5871db37ea88b4

    SuSE-8.1:
      
      e7488a05d07282bbd8317f834c24f0d4
      
      e6db8d49932368487a334d803572ed4e
      
      9c6c4ab2b8a461ca391a2453d05d9b71
    patch rpm(s):
      
      37960d363c09a1123c25b11d6a753968
      
      77d66503d21447bd1dd8339463c7b25b
      
      c747e07c307e9619cf04a3e2c8cc369f
    source rpm(s):
      
      952c96bc22740b252e151c27537e5c1b

    SuSE-8.0:
      
      7126396c99deb931dda869fdc8e5e6ef
      
      6cfa50d58f7b23201f2056d6097c4161
      
      23d978a491c8a0a0035142276ae9c806
    patch rpm(s):
      
      49833c754e880fba15e579ad32d6861c
      
      3eba782210bf2e3a714616571bea0066
      
      9d6d58e8da20ea06bfd3207c44925190
    source rpm(s):
      
      bc8db10701bdaee4da9776a6dc49fc29

    SuSE-7.3:
      
      f3171ff82e6d3fbf9913cfb58d984602
      
      db2fe45728f6073f15c6440538926828
      
      278a0338ed3a6ae65c7328f422f7abfc
    source rpm(s):
      
      c1076bca4b5a7d750f72811c097e92fa

    SuSE-7.2:
      
      2b5af68cb036119322a8a666fa68046b
      
      d1f95967eb77ff7b8761ec27795cb740
      
      e8cd7dda9473259239458b5e008c6924
    source rpm(s):
      
      e3c0693bda7d898ffc5bfb8f23478e7e


    Sparc Platform:

    SuSE-7.3:
      
      52a66dfd5f2f330240dab5e59c412ef7
      
      6060be5ff51994e0ab73e8afc7ba2f26
      
      802c951032a42b1b21f51ab53af502c9
    source rpm(s):
      
      350c8fcc5522c08ca9096803cc34dd42

    PPC Power PC Platform:

    SuSE-7.3:
      
      4dfbca3cbc9e9a3f8f36ab19a7bb4093
      
      068cbab05a37e74b9f57abcae7eb6b64
      
      c897ad4fa5a724c11efabbecfdd929c4
    source rpm(s):
      
      aa219acd13b73c45e2b418e8df03a1ee


______________________________________________________________________________

2)  Pending vulnerabilities in SuSE Distributions and Workarounds:

    - OpenSSL
    Critical bugs within the ASN.1 parsing routines have been reported recently.
    We are currently building new packages and will notify you in a separate
    advisory when the packages are available.

______________________________________________________________________________

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>