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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                MozillaFirefox,seamonkey
        Announcement ID:        SUSE-SA:2008:058
        Date:                   Fri, 19 Dec 2008 12:00:00 +0000
        Affected Products:      openSUSE 10.3
                                openSUSE 11.0
                                openSUSE 11.1
        Vulnerability Type:     remote code execution
        Severity (1-10):        8
        SUSE Default Package:   yes
        Cross-References:       CVE-2008-5500, CVE-2008-5501, CVE-2008-5502
                                CVE-2008-5503, CVE-2008-5505, CVE-2008-5506
                                CVE-2008-5507, CVE-2008-5508, CVE-2008-5510
                                CVE-2008-5511, CVE-2008-5512, CVE-2008-5513
                                MFSA 2008-60, MFSA 2008-61, MFSA 2008-63
                                MFSA 2008-64, MFSA 2008-65, MFSA 2008-66
                                MFSA 2008-67, MFSA 2008-68, MFSA 2008-69

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             Mozilla 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:
            See SUSE Security Summary Report
        6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

   The Mozilla Firefox browser was updated to version 3.0.5, fixing
   various security issues and stability problems.
   The Mozilla Seamonkey browser was updated to version 1.1.14, also
   fixing various security issues and stability problems.

   The other Mozilla browsers and suites are still being prepared and
   will be released when they have passed QA.


   The following security issues were fixed:

   MFSA 2008-69 / CVE-2008-5513: Mozilla security researcher moz_bug_r_a4
   reported vulnerabilities in the session-restore feature by which
   content could be injected into an incorrect document storage location,
   including storage locations for other domains. An attacker could
   utilize these issues to violate the browser's same-origin policy and
   perform an XSS attack while SessionStore data is being restored.
   moz_bug_r_a4 also reported that one variant could be used by an
   attacker to run arbitrary JavaScript with chrome privileges.

   MFSA 2008-68 / CVE-2008-5512 / CVE-2008-5511: Mozilla security
   researcher moz_bug_r_a4 reported that an XBL binding, when attached to
   an unloaded document, can be used to violate the same-origin policy and
   execute arbitrary JavaScript within the context of a different website.
   moz_bug_r_a4 also reported two vulnerabilities by which page content
   can pollute XPCNativeWrappers and run arbitrary JavaScript with chrome
   privileges.  Thunderbird shares the browser engine with Firefox and
   could be vulnerable if JavaScript were to be enabled in mail. This is
   not the default setting and we strongly discourage users from running
   JavaScript in mail.  Workaround Disable JavaScript until a version
   containing these fixes can be installed.

   MFSA 2008-67 / CVE-2008-5510: Kojima Hajime reported that unlike
   literal null characters which were handled correctly, the escaped
   form '\0' was ignored by the CSS parser and treated as if it was
   not present in the CSS input string. This issue could potentially be
   used to bypass script sanitation routines in web applications. The
   severity of this issue was determined to be low.


   MFSA 2008-66 / CVE-2008-5508: Perl developer Chip Salzenberg reported
   that certain control characters, when placed at the beginning of a
   URL, would lead to incorrect parsing resulting in a malformed URL
   being output by the parser. IBM researchers Justin Schuh, Tom Cross,
   and Peter William also reported a related symptom as part of their
   research that resulted in MFSA 2008-37.  There was no direct security
   impact from this issue and its effect was limited to the improper
   rendering of hyperlinks containing specific characters. The severity
   of this issue was determined to be low.


   MFSA 2008-65 / CVE-2008-5507: Google security researcher Chris Evans
   reported that a website could access a limited amount of data from
   a different domain by loading a same-domain JavaScript URL which
   redirects to an off-domain target resource containing data which
   is not parsable as JavaScript. Upon attempting to load the data as
   JavaScript a syntax error is generated that can reveal some of the
   file context via the window.onerror DOM API.  This issue could be
   used by a malicious website to steal private data from users who are
   authenticated on the redirected website. How much data could be at risk
   would depend on the format of the data and how the JavaScript parser
   attempts to interpret it. For most files the amount of data that can
   be recovered would be limited to the first word or two. Some data files
   might allow deeper probing with repeated loads.  Thunderbird shares the
   browser engine with Firefox and could be vulnerable if JavaScript were
   to be enabled in mail. This is not the default setting and we strongly
   discourage users from running JavaScript in mail.  Workaround Disable
   JavaScript until a version containing these fixes can be installed.

   MFSA 2008-64 / CVE-2008-5506: Marius Schilder of Google Security
   reported that when a XMLHttpRequest is made to a same-origin resource
   which 302 redirects to a resource in a different domain, the response
   from the cross-domain resource is readable by the site issuing the
   XHR. Cookies marked HttpOnly were not readable, but other potentially
   sensitive data could be revealed in the XHR response including URL
   parameters and content in the response body.  Thunderbird shares the
   browser engine with Firefox and could be vulnerable if JavaScript were
   to be enabled in mail. This is not the default setting and we strongly
   discourage users from running JavaScript in mail.  Workaround Disable
   JavaScript until a version containing these fixes can be installed.


   MFSA 2008-63 / CVE-2008-5505: Security researcher Hish reported
   that the persist attribute in XUL elements can be used to store
   cookie-like information on a user's computer which could later be
   read by a website. This creates a privacy issue for users who have a
   non-standard cookie preference and wish to prevent sites from setting
   cookies on their machine. Even with cookies turned off, this issue
   could be used by a website to write persistent data in a user's
   browser and track the user across browsing sessions. Additionally,
   this issue could allow a website to bypass the limits normally placed
   on cookie size and number.

   MFSA 2008-60 / CVE-2008-5502 / CVE-2008-5501 / CVE-2008-5500: 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.  Thunderbird shares
   the browser engine with Firefox and could be vulnerable if JavaScript
   were to be enabled in mail. This is not the default setting and we
   strongly discourage users from running JavaScript in mail. Without
   further investigation we cannot rule out the possibility that for some
   of these an attacker might be able to prepare memory for exploitation
   through some means other than JavaScript such as large images.
   Workaround Disable JavaScript until a version containing these fixes
   can be installed.

2) Solution or Work-Around

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

3) Special Instructions and Notes

   Please close and restart Mozilla Firefox and/or seamonkey 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 11.1:
                                       
   openSUSE 11.0:
                                    
   openSUSE 10.3:
                  
   x86-64 Platform:

   openSUSE 11.1:
         
   openSUSE 11.0:
         
   Sources:

   openSUSE 11.1:
         
   openSUSE 11.0:
         
   openSUSE 10.3:
   
______________________________________________________________________________

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