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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                phpMyAdmin
        Announcement ID:        SUSE-SA:2006:004
        Date:                   Thu, 26 Jan 2006 13: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):        5
        SUSE Default Package:   no
        Cross-References:       CVE-2005-3665, CVE-2005-3787, CVE-2005-4079

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             phpMyAdmin Variable Overwrite Vulnerability
           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

   Stefan Esser discovered a bug in in the register_globals emulation
   of phpMyAdmin that allowes to overwrite variables. An attacker could
   exploit the bug to ultimately execute code (CVE-2005-4079).
   Additionally several cross-site-scripting bugs were discovered
   (CVE-2005-3787, CVE-2005-3665).
   
   We have released a version update to phpMyAdmin-2.7.0-pl2 which
   addresses the issues mentioned above.

2) Solution or Work-Around

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

3) Special Instructions and Notes

   Please close and restart your web server after the update.
   
   Attention: The new phpMyAdmin version requires either php4-session or
   php5-session depending on whether you use php4 or php5. Make sure
   the correct package is installed otherwise phpMyAdmin will not work
   anymore after the update.

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:
             7cbc7af360dd5791f869cbebfe3219d6
   
   SUSE LINUX 9.3:
             a4b3baf33c3f9426e7ca54d555b3c078
   
   SUSE LINUX 9.2:
             0b8714574f839b323ba597d64b353afb
   
   SUSE LINUX 9.1:
             7b7c5fb9142964cc9938967660ae0bda
             9bded98b55cd1249de2b894fce828a4e
   
   SuSE Linux 9.0:
             a7cab5e6787daa6b17995c0e505c2ca9
             ae7a60bd21a2fe3de1607d5d806e5ae9
   
   Sources:
   
   SUSE LINUX 10.0:
             0b73e931f2d7506ff6d0d5a7560a2aa2
   
   SUSE LINUX 9.3:
             9bd61252a955b01ab1ea685185388bc7
   
   SUSE LINUX 9.2:
             8c9216ec3c9ef219a4d60041c672b52c
   
   SUSE LINUX 9.1:
             b9632cade67e8c7a4b8505492fd3f027
             d15b9c02417f88d427c1ab35434b561c
   
   SuSE Linux 9.0:
             36f045d6238c0d39b2ec83cd2b7d8811
             0e0fcc76ddf4304461a1f0ab4e015cc0

______________________________________________________________________________

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