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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                MozillaFirefox
        Announcement ID:        SUSE-SA:2009:023
        Date:                   Mon, 20 Apr 2009 11:00:00 +0000
        Affected Products:      openSUSE 10.3
                                SUSE Linux Enterprise Desktop 10 SP2
                                SUSE Linux Enterprise 10 SP2 DEBUGINFO
                                SUSE Linux Enterprise Server 10 SP2
        Vulnerability Type:     remote code execution
        Severity (1-10):        8
        SUSE Default Package:   yes
        Cross-References:       CVE-2009-0040, CVE-2009-0352, CVE-2009-0353
                                CVE-2009-0772, CVE-2009-0774, CVE-2009-0776
                                CVE-2009-1169, MFSA 2009-01, MFSA 2009-07
                                MFSA 2009-09, MFSA 2009-10, MFSA 2009-12

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             Mozilla Firefox 2 security update
           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 Mozilla Firefox Browser was refreshed to the current MOZILLA_1_8
   branch state around fix level 2.0.0.22, backporting various security
   fixes from the Firefox 3.0.8 browser version.

   Security issues identified as being fixed are:
   MFSA 2009-01 / CVE-2009-0352 / CVE-2009-0353: Mozilla developers   identified and fixed several stability bugs in the browser engine used
   in Firefox and other Mozilla-based products. Some of these crashes
   showed evidence of memory corruption under certain circumstances and
   we presume that with enough effort at least some of these could be
   exploited to run arbitrary code.

   MFSA 2009-07 / CVE-2009-0772 / CVE-2009-0774: Mozilla developers   identified and fixed several stability bugs in the browser engine used
   in Firefox and other Mozilla-based products. Some of these crashes
   showed evidence of memory corruption under certain circumstances and
   we presume that with enough effort at least some of these could be
   exploited to run arbitrary code.

   MFSA 2009-09 / CVE-2009-0776: Mozilla security researcher Georgi
   Guninski reported that a website could use nsIRDFService and a
   cross-domain redirect to steal arbitrary XML data from another domain,
   a violation of the same-origin policy. This vulnerability could be used
   by a malicious website to steal private data from users authenticated
   to the redirected website.

   MFSA 2009-10 / CVE-2009-0040: Google security researcher Tavis
   Ormandy reported several memory safety hazards to the libpng project,
   an external library used by Mozilla to render PNG images. These
   vulnerabilities could be used by a malicious website to crash a
   victim's browser and potentially execute arbitrary code on their
   computer. libpng was upgraded to version 1.2.35 which contains fixes
   for these flaws.

   MFSA 2009-12 / CVE-2009-1169: Security researcher Guido Landi
   discovered that a XSL stylesheet could be used to crash the browser
   during a XSL transformation. An attacker could potentially use this
   crash to run arbitrary code on a victim's computer.
   This vulnerability was also previously reported as a stability problem
   by Ubuntu community member, Andre. Ubuntu community member Michael
   Rooney reported Andre's findings to Mozilla, and Mozilla community
   member Martin helped reduce Andre's original test case and contributed
   a patch to fix the vulnerability.

2) Solution or Work-Around

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

3) Special Instructions and Notes

   Please close and restart all running instances of Firefox 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.


   x86 Platform:

   openSUSE 10.3:
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/10.3/rpm/i586/MozillaFirefox-2.0.0.21post-0.1.i586.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/10.3/rpm/i586/MozillaFirefox-translations-2.0.0.21post-0.1.i586.rpm

   Power PC Platform:

   openSUSE 10.3:
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/10.3/rpm/ppc/MozillaFirefox-2.0.0.21post-0.1.ppc.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/10.3/rpm/ppc/MozillaFirefox-translations-2.0.0.21post-0.1.ppc.rpm

   x86-64 Platform:

   openSUSE 10.3:
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/10.3/rpm/x86_64/MozillaFirefox-2.0.0.21post-0.1.x86_64.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/10.3/rpm/x86_64/MozillaFirefox-translations-2.0.0.21post-0.1.x86_64.rpm

   Sources:

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

   SUSE Linux Enterprise Server 10 SP2
   SUSE Linux Enterprise Desktop 10 SP2
   SUSE Linux Enterprise 10 SP2 DEBUGINFO
     https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=9ac5f072355543bb38c9916ea1c73aba

______________________________________________________________________________

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.

    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.

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

    opensuse-security@opensuse.org
        -   General Linux and SUSE security discussion.
            All SUSE security announcements are sent to this list.
            To subscribe, send an e-mail to
                .

    opensuse-security-announce@opensuse.org
        -   SUSE's announce-only mailing list.
            Only SUSE's security announcements are sent to this list.
            To subscribe, send an e-mail to
                .

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