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 Advisory Watch: March 27th, 2015
Linux Security Week: March 23rd, 2015
LinuxSecurity Newsletters
Choose Lists:
About our Newsletters
RSS Feeds
Get the LinuxSecurity news you want faster with RSS
Powered By

SuSE: MozillaFirefox (SUSE-SA:2007:019) Print E-mail
User Rating:      How can I rate this item?
Posted by Benjamin D. Thomas   
SuSE Updated package.

                        SUSE Security Announcement

        Package:                MozillaFirefox,seamonkey
        Announcement ID:        SUSE-SA:2007:019
        Date:                   Tue, 06 Mar 2007 18:00:00 +0000
        Affected Products:      SUSE LINUX 9.3
                                SUSE LINUX 10.0
                                SUSE LINUX 10.1
                                openSUSE 10.2
                                Novell Linux Desktop 9
                                SUSE SLED 10
                                SUSE SLES 10
        Vulnerability Type:     remote code execution
        Severity (1-10):        6
        SUSE Default Package:   yes
        Cross-References:       CVE-2006-6077, CVE-2007-0008, CVE-2007-0009
                                CVE-2007-0775, CVE-2007-0776, CVE-2007-0777
                                CVE-2007-0778, CVE-2007-0779, CVE-2007-0780
                                CVE-2007-0800, CVE-2007-0981, CVE-2007-0994
                                CVE-2007-0995, CVE-2007-0996, CVE-2007-1092
                                MFSA 2006-72, MFSA 2007-01, MFSA 2007-02
                                MFSA 2007-03, MFSA 2007-04, MFSA 2007-05
                                MFSA 2007-06, MFSA 2007-08, MFSA 2007-09

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             Mozilla Firefox security release /
           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 web browser was updated to security update version on older products and Mozilla Firefox to version on
   openSUSE 10.2 to fix various security issues.

   Updates for the Mozilla seamonkey suite before 10.2, Mozilla Suite
   and Mozilla Thunderbird are still pending.

   Full details can be found on:

   - MFSA 2007-01: As part of the Firefox  and update
     releases several bugs were fixed to improve the stability of the
     browser. Some of these were crashes that showed evidence of memory
     corruption and we presume that with enough effort at least some of
     these could be exploited to run arbitrary code. These fixes affected
     the layout engine (CVE-2007-0775), SVG renderer (CVE-2007-0776)
     and javascript engine (CVE-2007-0777).

   - MFSA 2007-02: Various enhancements were done to make XSS exploits
     against websites less effective. These included fixes for invalid
     trailing characters (CVE-2007-0995), child frame character set
     inheritance (CVE-2007-0996), password form injection (CVE-2006-6077),
     and the Adobe Reader universal XSS problem.

   - MFSA 2007-03/CVE-2007-0778: AAd reported a potential disk cache
     collision that could be exploited by remote attackers to steal
     confidential data or execute code.

   - MFSA 2007-04/CVE-2007-0779: David Eckel reported that browser UI
     elements--such as the host name and security indicators--could be
     spoofed by using a large, mostly transparent, custom cursor and
     adjusting the CSS3 hot-spot property so that the visible part of
     the cursor floated outside the browser content area.

   - MFSA 2007-05: Manually opening blocked popups could be exploited by
     remote attackers to allow XSS attacks (CVE-2007-0780) or to execute
     code in local files (CVE-2007-0800).

   - MFSA 2007-06:
     Two buffer overflows were found in the NSS handling of Mozilla.

     CVE-2007-0008: SSL clients such as Firefox and Thunderbird can suffer
     a buffer overflow if a malicious server presents a certificate
     with a public key that is too small to encrypt the entire "Master
     Secret". Exploiting this overflow appears to be unreliable but
     possible if the SSLv2 protocol is enabled.

     CVE-2007-0009: Servers that use NSS for the SSLv2 protocol can
     be exploited by a client that presents a "Client Master Key" with
     invalid length values in any of several fields that are used without
     adequate error checking. This can lead to a buffer overflow that
     presumably could be exploitable.

   - MFSA 2007-06/CVE-2007-0981: Michal Zalewski demonstrated that setting
     location.hostname to a value with embedded null characters can
     confuse the browsers domain checks. Setting the value triggers a
     load, but the networking software reads the hostname only up to
     the null character while other checks for "parent domain" start at
     the right and so can have a completely different idea of what the
     current host is.

   - MFSA 2007-08/CVE-2007-1092: Michal Zalewski reported a memory
     corruption vulnerability in Firefox involving mixing
     the onUnload event handler and self-modifying document.write()
     calls. This flaw was introduced in Firefox and and
     does not affect earlier versions; it is fixed in Firefox

   - MFSA 2007-09/CVE-2007-0994: moz_bug_r_a4 reports that the fix for
     MFSA 2006-72 in Firefox and Firefox introduced a
     regression that allows scripts from web content to execute arbitrary
     code by setting the src attribute of an IMG tag to a specially
     crafted javascript: URI.
     The same regression also caused javascript: URIs in IMG tags to be
     executed even if JavaScript execution was disabled in the global
     preferences. This facet was noted by moz_bug_r_a4 and reported
     independently by Anbo Motohiko.

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.2:

   SUSE LINUX 10.1:

   SUSE LINUX 10.0:

   SUSE LINUX 9.3:

   Power PC Platform:

   openSUSE 10.2:

   SUSE LINUX 10.1:

   SUSE LINUX 10.0:

   x86-64 Platform:

   openSUSE 10.2:


   openSUSE 10.2:

   SUSE LINUX 10.1:

   SUSE LINUX 10.0:

   SUSE LINUX 9.3:

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

   Novell Linux Desktop 9

   Novell Linux Desktop 9 for x86




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

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


       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, 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

  - 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
Weekend Edition
FBI Quietly Removes Recommendation To Encrypt Your Phone
And the prize for LEAST SECURE BROWSER goes to ... Chrome!
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.