SUSE Security Advisory: 2005-036 Important for Mozilla Firefox Exploit Risk

Warning: Undefined array key "advisoryid" in /var/www/www.linuxsecurity.com-443/html/tmp/regularlabs/custom_php/3730797_1edcd913e2b52798c5b9126b8927230e on line 19

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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                MozillaFirefox
        Announcement ID:        SUSE-SA:2005:030
        Date:                   Thu, 09 Jun 2005 12:00:00 +0000
        Affected Products:      9.0, 9.1, 9.2, 9.3
                                Novell Linux Desktop 9

        Vulnerability Type:     remote code execution
        Severity (1-10):        8
        SUSE Default Package:   yes
        Cross-References:       MFSA 2005-44
                                MFSA 2005-43
                                MFSA 2005-42
                                CAN-2005-1532
                                CAN-2005-1531

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             various Mozilla Firefox security problems
           Problem Description
        2) Solution or Work-Around
        3) Special Instructions and Notes
        4) Package Location and Checksums
        5) Pending Vulnerabilities, Solutions, and Work-Arounds:
            none
        6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

   This update upgrades Mozilla Firefox to version 1.0.4, fixing the
   following security problems:

   MFSA 2005-42:
   A problem in the install confirmation dialog together with a bad fix
   for MFSA 2005-41 allowed a remote attacker to execute arbitrary code
   with the help of a cross site scripting problem on the Mozilla website.

   The Mozilla website has been fixed so this is no real problem anymore.

   MFSA 2005-43/CAN-2005-1531:
   By causing a frame to navigate back to a previous javascript: URL an
   attacker can inject script into the forward site. This site can be
   controlled by the attacker allowing them to steal cookies or sensitive
   data from that page or to perform actions on behalf of that user.

   MFSA 2005-44/CAN-2005-1532:
   A variant of MFSA 2005-41 overrides properties on a non-DOM node and
   then substitutes that object for one chrome script will access. Most
   examples involved the attacker synthesizing an event targeted at a
   non-DOM node, and overriding standard DOM node properties such as
   type with references to eval() calls or Script() objects.

   The MFSA-2005-43 and MFSA-2005-44 flaws also affect the Mozilla
   Suite browsers. We are working on updates for those.

   Updated packages were already released on May 20th. We wanted to
   postpone the advisory until we have fixed packages for the Mozilla
   Suite, but these will take some more time.


2) Solution or Work-Around

   Install the updated packages.

3) Special Instructions and Notes

   Please restart the Firefox web browser after installing the updates.

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 file name of the
   downloaded RPM package.

   Our maintenance customers are notified individually. The packages are
   offered for installation from the maintenance web.


   x86 Platform:

   SUSE Linux 9.3:
             6d9eaaba4ac8c3ce26b6d2855c540064
             2c5a8918a90873355632c6bc2a01df4d

   SUSE Linux 9.2:
             ae767fe1c07c1e211b87f49944f8c73c

   SUSE Linux 9.1:
             c2d7129c2c542ead51cd53730b670a2c
   source rpm(s):
             bad2b3f61a29d9e02bfb8d48b0303885

   SUSE Linux 9.0:
             e7f0eb745a9780f94548078130af0337
   source rpm(s):
             12f2af97b563fdc0dfebb51aba2a9797

   x86-64 Platform:

   SUSE Linux 9.2:
             dd4631648bfa4671ab96a683b3ded7ef
   source rpm(s):
             31316daa8130a32e2b7d14d0a4c7019a

   SUSE Linux 9.1:
             1af6dcde322f8fb8d1fdbf6dd0780462
   source rpm(s):
             e1d4c3104c836e36a0bca49d358410ac

   SUSE Linux 9.0:
             247e4c5411e9f10c50fad8f9f6634523
   source rpm(s):
             d7e393be6d9080ea0038b831ce8a1204


______________________________________________________________________________

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