Share your story
The central voice for Linux and Open Source security news
Home News Topics Advisories HOWTOs Features Newsletters About Register

Sign up!
EnGarde Community
What is the most important Linux security technology?
Linux Events
Linux User Groups
Link to Us
Security Center
Book Reviews
Security Dictionary
Security Tips
White Papers
Featured Blogs
All About Linux
DanWalsh LiveJournal
Latest Newsletters
Linux Security Week: March 23rd, 2015
Linux Advisory Watch: March 20th, 2015
LinuxSecurity Newsletters
Choose Lists:
About our Newsletters
RSS Feeds
Get the LinuxSecurity news you want faster with RSS
Powered By

SuSE: Mozilla Firefox (SUSE-SA:2009:009) Print E-mail
User Rating:      How can I rate this item?
Posted by Benjamin D. Thomas   
SuSE The Mozilla Firefox browser is updated to version 3.0.6 fixing various security and stability issues.

                        SUSE Security Announcement

        Package:                MozillaFirefox
        Announcement ID:        SUSE-SA:2009:009
        Date:                   Mon, 16 Feb 2009 10:00:00 +0000
        Affected Products:      openSUSE 11.0
                                openSUSE 11.1
        Vulnerability Type:     remote code execution
        Severity (1-10):        8
        SUSE Default Package:   yes
        Cross-References:       CVE-2009-0352, CVE-2009-0353, CVE-2009-0354
                                CVE-2009-0355, CVE-2009-0356, CVE-2009-0357
                                CVE-2009-0358, MFSA 2008-47, MFSA 2009-01
                                MFSA 2009-02, MFSA 2009-03, MFSA 2009-04
                                MFSA 2009-05, MFSA 2009-06

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             Mozilla Firefox 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 is updated to version 3.0.6 fixing various
   security and stability issues.

   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-02 / CVE-2009-0354: Mozilla security researcher moz_bug_r_a4
   reported that a chrome XBL method can be used in conjunction with
   window.eval to execute arbitrary JavaScript within the context of
   another website, violating the same origin policy. Firefox 2 releases
   are not affected.

   MFSA 2009-03 / CVE-2009-0355: Mozilla security researcher moz_bug_r_a4
   reported that a form input controls type could be changed during the
   restoration of a closed tab. An attacker could set an input controls
   text value to the path of a local file whose location was known to
   the attacker. If the tab was then closed and the victim persuaded
   to re-open it, upon restoring the tab the attacker could use this
   vulnerability to change the input type to file. Scripts in the page
   could then automatically submit the form and steal the contents of
   the user's local file.

   MFSA 2009-04 / CVE-2009-0356: Mozilla security researcher Georgi
   Guninski reported that the fix for an earlier vulnerability reported
   by Liu Die Yu using local internet shortcut files to access other
   sites (MFSA 2008-47) could be bypassed by redirecting to a privileged
   about: URI such as about:plugins. If an attacker could get a victim
   to download two files, a malicious HTML file and a .desktop shortcut
   file, they could have the HTML document load a privileged chrome
   document via the shortcut and both documents would be treated as same
   origin. This vulnerability could potentially be used by an attacker
   to inject arbitrary code into the chrome document and execute with
   chrome privileges. Because this attack has relatively high complexity,
   the severity of this issue was determined to be moderate.

   MFSA 2009-05 / CVE-2009-0357: Developer and Mozilla community
   member Wladimir Palant reported that cookies marked HTTPOnly were
   readable by JavaScript via the XMLHttpRequest.getResponseHeader and
   XMLHttpRequest.getAllResponseHeaders APIs. This vulnerability bypasses
   the security mechanism provided by the HTTPOnly flag which intends to
   restrict JavaScript access to document.cookie.
   The fix prevents the XMLHttpRequest feature from accessing the
   Set-Cookie and Set-Cookie2 headers of any response whether or not
   the HTTPOnly flag was set for those cookies.

   MFSA 2009-06 / CVE-2009-0358: Paul Nel reported that certain HTTP
   directives to not cache web pages, Cache-Control: no-store and
   Cache-Control: no-cache for HTTPS pages, were being ignored by
   Firefox 3. On a shared system, applications relying upon these HTTP
   directives could potentially expose private data. Another user on the
   system could use this vulnerability to view improperly cached pages
   containing private data by navigating the browser back.

   Fixes for older Firefox and other Mozilla versions are being worked on.

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 Mozilla 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 11.1:

   openSUSE 11.0:

   Power PC Platform:

   openSUSE 11.1:

   openSUSE 11.0:

   x86-64 Platform:

   openSUSE 11.1:

   openSUSE 11.0:


   openSUSE 11.1:

   openSUSE 11.0:


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

      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

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

    The information in this advisory may be distributed or reproduced,
    provided that the advisory is not modified in any way. In particular, the
    clear text signature should show proof of the authenticity of the text.

    SUSE Linux Products GmbH provides no warranties of any kind whatsoever
    with respect to the information contained in this security advisory.
< Prev   Next >


Latest Features
Peter Smith Releases Linux Network Security Online
Securing a Linux Web Server
Password guessing with Medusa 2.0
Password guessing as an attack vector
Squid and Digest Authentication
Squid and Basic Authentication
Demystifying the Chinese Hacking Industry: Earning 6 Million a Night
Free Online security course (LearnSIA) - A Call for Help
What You Need to Know About Linux Rootkits
Review: A Practical Guide to Fedora and Red Hat Enterprise Linux - Fifth Edition
Yesterday's Edition
Tech Companies, Privacy Advocates Call for NSA Reform
Google warns of unauthorized TLS certificates trusted by almost all OSes
How Kevin Mitnick hacked the audience at CeBIT 2015
Partner Sponsor

Community | HOWTOs | Blogs | Features | Book Reviews | Networking
 Security Projects |  Latest News |  Newsletters |  SELinux |  Privacy |  Home
 Hardening |   About Us |   Advertise |   Legal Notice |   RSS |   Guardian Digital
(c)Copyright 2015 Guardian Digital, Inc. All rights reserved.