-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                phpMyAdmin
        Announcement ID:        SUSE-SA:2005:066
        Date:                   Fri, 18 Nov 2005 11:00:00 +0000
        Affected Products:      SUSE LINUX 10.0
                                SUSE LINUX 9.3
                                SUSE LINUX 9.2
                                SUSE LINUX 9.1
                                SuSE Linux 9.0
        Vulnerability Type:     remote code execution
        Severity (1-10):        7
        SUSE Default Package:   no
        Cross-References:       CVE-2005-2869, CVE-2005-3300, CVE-2005-3301
                                PMASA-2005-5

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             multiple security problems in phpMyAdmin
           Problem Description
        2) Solution or Work-Around
        3) Special Instructions and Notes
        4) Package Location and Checksums
        5) Pending Vulnerabilities, Solutions, and Work-Arounds:
            See SUSE Security Summary Report.
        6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

   The MySQL configuration frontend phpMyAdmin was updated to fix
   the following security problems which can be remotely exploited:
   
   - Multiple cross-site scripting (XSS) bugs (CVE-2005-3301,
     CVE-2005-2869, PMASA-2005-5).
   
   - Multiple file inclusion vulnerabilities that allowed an attacker
     to include arbitrary files (CVE-2005-3300, CVE-2005-3301,
     PMASA-2005-5).

2) Solution or Work-Around

   There is no known workaround, please install the update packages.

3) Special Instructions and Notes

   None.

4) Package Location and Checksums

   The preferred method for installing security updates is to use the YaST
   Online Update (YOU) tool. YOU detects which updates are required and
   automatically performs the necessary steps to verify and install them.
   Alternatively, download the update packages for your distribution manually
   and verify their integrity by the methods listed in Section 6 of this
   announcement. Then install the packages using the command

     rpm -Fhv 

   to apply the update, replacing  with the filename of the
   downloaded RPM package.

   
   Platform Independent:
   
   SUSE LINUX 10.0:
             98fb372df6fbb616bbc3352ed83db7e8
   
   SUSE LINUX 9.3:
             99149187c8d0a9b6cbe144723bbcbc4c
   
   SUSE LINUX 9.2:
             00db8b743c780dbc730356097a4f163a
   
   SUSE LINUX 9.1:
             d101d0e68c49a9ed2dd2c4358ff87104
             74d37eba2dfc928700a573402c0dfc2e
   
   SuSE Linux 9.0:
             8af75dcd104b8be4bf77e0bb5c1f116d
             1f2ef8a90a212d99603a866a453dfb04
   
   Sources:
   
   SUSE LINUX 10.0:
             cdd5526c185af3651bef319950f80a7d
   
   SUSE LINUX 9.3:
             04e009aa9015d37315c557e7599ff163
   
   SUSE LINUX 9.2:
             30e6770d3d70799aa069c2d936c19eac
   
   SUSE LINUX 9.1:
             4d5fe0f490d25245c029e1da7b04ee56
             e1935f0f2aba552f18d028110ddd52d9
   
   SuSE Linux 9.0:
             8ae59fb9f3be6cc23581746f6c2be7fb
             ff8032bcc6bc197780a74b18fdb4ac5d

______________________________________________________________________________

5) Pending Vulnerabilities, Solutions, and Work-Arounds:

   See SUSE Security Summary Report.
______________________________________________________________________________

6) Authenticity Verification and Additional Information

  - Announcement authenticity verification:

    SUSE security announcements are published via mailing lists and on Web
    sites. The authenticity and integrity of a SUSE security announcement is
    guaranteed by a cryptographic signature in each announcement. All SUSE
    security announcements are published with a valid signature.

    To verify the signature of the announcement, save it as text into a file
    and run the command

      gpg --verify 

    replacing  with the name of the file where you saved the
    announcement. The output for a valid signature looks like:

      gpg: Signature made  using RSA key ID 3D25D3D9
      gpg: Good signature from "SuSE Security Team "

    where  is replaced by the date the document was signed.

    If the security team's key is not contained in your key ring, you can
    import it from the first installation CD. To import the key, use the
    command

      gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc

  - Package authenticity verification:

    SUSE update packages are available on many mirror FTP servers all over the
    world. While this service is considered valuable and important to the free
    and open source software community, the authenticity and the integrity of
    a package needs to be verified to ensure that it has not been tampered
    with.

    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) Using the internal gpg signatures of the rpm package
    2) MD5 checksums as provided in this announcement

    1) The internal 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, replacing  with the
       filename of the RPM package downloaded. The package is unmodified if it
       contains a valid signature from build@suse.de with the key ID 9C800ACA.

       This key is automatically imported into the RPM database (on
       RPMv4-based distributions) and the gpg key ring of 'root' during
       installation. You can also find it on the first installation CD and at
       the end of this announcement.

    2) If you need an alternative means of verification, use the md5sum
       command to verify the authenticity of the packages. 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
       SUSE security announcement. Because the announcement containing the
       checksums is cryptographically signed (by security@suse.de), the
       checksums show proof of the authenticity of the package if the
       signature of the announcement is valid. Note that the md5 sums
       published in the SUSE Security Announcements are valid for the
       respective packages only. Newer versions of these packages cannot be
       verified.

  - SUSE runs two security mailing lists to which any interested party may
    subscribe:

    suse-security@suse.com
        -   General Linux and SUSE security discussion.
            All SUSE security announcements are sent to this list.
            To subscribe, send an e-mail 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 e-mail to
                .

    For general information or the frequently asked questions (FAQ),
    send mail to  or
    .

    ====================================================================    SUSE's security contact is  or .
    The  public key is listed below.
    ====================================================================