-----BEGIN PGP SIGNED MESSAGE-----

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                mysql
        Announcement-ID:        SUSE-SA:2005:019
        Date:                   Thu, 24 Mar 2005 16:00:00 +0000
        Affected products:      8.2, 9.0, 9.1, 9.2
                                SUSE Linux Desktop 1.0
                                SUSE Linux Enterprise Server 8, 9
                                Novell Linux Desktop 9
        Vulnerability Type:     remote code execution
        Severity (1-10):        6
        SUSE default package:   no
        Cross References:       CAN-2005-0709
                                CAN-2005-0710
                                CAN-2005-0711

    Content of this advisory:
        1) security vulnerability resolved:
             security problems in mysql
           problem description
        2) solution/workaround
        3) special instructions and notes
        4) package location and checksums
        5) pending vulnerabilities, solutions, workarounds:
            See SUSE Security Summary Report (after Easter).

        6) standard appendix (further information)

______________________________________________________________________________

1) problem description, brief discussion

    MySQL is an Open Source database server, commonly used together with
    web services provided by PHP scripts or similar.

    This security update fixes a broken mysqlhotcopy script as well as
    several security related bugs:

    - CAN-2005-0709: MySQL allowed remote authenticated users with
      INSERT and DELETE privileges to execute arbitrary code by using
      CREATE FUNCTION to access libc calls, as demonstrated by using strcat,
      on_exit, and exit.

    - CAN-2005-0710: MySQL allowed remote authenticated users with
      INSERT and DELETE privileges to bypass library path restrictions
      and execute arbitrary libraries by using INSERT INTO to modify the
      mysql.func table, which is processed by the udf_init function.

    - CAN-2005-0711: MySQL used predictable file names when creating
      temporary tables, which allows local users with CREATE TEMPORARY
      TABLE privileges to overwrite arbitrary files via a symlink attack.


    The first two vulnerabilities can be exploited by an attacker using
    SQL inject attack vectors into a flawed PHP application for instance.


2) solution/workaround

    None. Please install the updated packages.

3) special instructions and notes

    Please restart the mysql database server update the update by
    running as root:

         /sbin/rcmysql try-restart


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.


    x86 Platform:

    SUSE Linux 9.2:
               9060e74c421f30d85d24d9029c6779b3
               66f6252369c5297629a3643d169776cf

    SUSE Linux 9.1:
               a485a73bb70f87a8921b5a12c4b27658
               0ab12a132ed5abe038457a538acf4ac3
    source rpm(s):
               63d0ad89fb1d031409098f981d92a011

    SUSE Linux 9.0:
               a24632927f128f1325614629333bddbc
               c054fffbcbd661408573f037935a69d0
    source rpm(s):
               1a4d0af904c7a797f001c093c1cbc2f1

    SUSE Linux 8.2:
               4af88dde3c487b0c7fcf22cb49d02b07
               e3a53abf26170957f532ea7ac25cdcd7
    source rpm(s):
               a50b1b6df881d203ec215b31bc73d698

    x86-64 Platform:

    SUSE Linux 9.2:
               6656f6ed35d92127ce298134a0624867
               79e4561d475e7bb2303f4ff41f553bb9
    source rpm(s):
               80b0820c075876a447a31952a67e6a5c

    SUSE Linux 9.1:
               c308aac4a2c273f983aa0a57722930b3
               d895c752111c215161e06d0bf88abf20
    source rpm(s):
               c5902748d9708ec5f4a76028e96de91a

    SUSE Linux 9.0:
               bfadabeab279bd0dccdad2cc04561e86
               485cc2aab05494fa7d8137bdd5ded701
    source rpm(s):
               ac5d1d6e78cbfed6307721490cf1c708


______________________________________________________________________________

5)  Pending vulnerabilities in SUSE Distributions and Workarounds:

    See SUSE Security Summary Report (after Easter).

______________________________________________________________________________

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.

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

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

    ====================================================================    SUSE's security contact is  or .
@suse.de>.
    The  public key is listed below.
    ====================================================================