copyright | disclaimer | privacy | contact  
Australia's Leading Computer Emergency Response Team
Search this site

On this site

 > About AusCERT
 > Membership
 > Contact Us
 > PKI Services
 > Publications
 > Sec. Bulletins
 > Conferences
 > News & Media
 > Services
 > Web Log
 > Site Map
 > Site Help
 > Member login


ASB-2012.0037 - [Win][UNIX/Linux] Firefox, Thunderbird and SeaMonkey: Multiple vulnerabilities

Date: 14 March 2012
References: ESB-2012.0279  ESB-2012.0280  ESB-2012.0284  ESB-2012.0287  ESB-2012.0303  ESB-2012.0404  

Click here for printable version
Click here for PGP verifiable version
Hash: SHA1

                         AUSCERT Security Bulletin

            New versions of Firefox, Thunderbird, and SeaMonkey
                               14 March 2012


        AusCERT Security Bulletin Summary

Product:              Firefox
Operating System:     Windows
                      UNIX variants (UNIX, Linux, OSX)
Impact/Access:        Execute Arbitrary Code/Commands -- Remote with User Interaction
                      Cross-site Scripting            -- Remote with User Interaction
                      Denial of Service               -- Remote with User Interaction
                      Provide Misleading Information  -- Remote with User Interaction
                      Access Confidential Data        -- Remote with User Interaction
Resolution:           Patch/Upgrade
CVE Names:            CVE-2012-0464 CVE-2012-0463 CVE-2012-0462
                      CVE-2012-0461 CVE-2012-0460 CVE-2012-0459
                      CVE-2012-0458 CVE-2012-0457 CVE-2012-0456
                      CVE-2012-0455 CVE-2012-0454 CVE-2012-0451
Member content until: Friday, April 13 2012


        Many vulnerabilities have been fixed in Mozilla Firefox and
        Thunderbird and in SeaMonkey.[1,2,3,4,5,6,7,8]


        The vendor has provided the following details about the vulnerabilities:
        "Security researchers Blair Strang and Scott Bell of Security Assessment
        found that when a parent window spawns and closes a child window that
        uses the file open dialog, a crash can be induced in shlwapi.dll on
        32-bit Windows 7 systems. This crash may be potentially exploitable." [1]
        "Firefox prevents the dropping of javascript: links onto a frame to
        prevent malicious sites from tricking users into performing a cross-site
        scripting (XSS) attacks on themselves. Security researcher Soroush
        Dalili reported a way to bypass this protection." [2]
        "Security researcher Atte Kettunen from OUSPG found two issues with
        Firefox's handling of SVG using the Address Sanitizer tool. The first
        issue, critically rated, is a use-after-free in SVG animation that
        could potentially lead to arbitrary code execution. The second issue
        is rated moderate and is an out of bounds read in SVG Filters. This
        could potentially incorporate data from the user's memory, making it
        accessible to the page content." [3]
        "Security Researcher Mike Brooks of Sitewatch reported that if multiple
        Content Security Policy (CSP) headers are present on a page, they have
        an additive effect page policy. Using carriage return line feed (CRLF)
        injection, a new CSP rule can be introduced which allows for cross-site
        scripting (XSS) on sites with a separate header injection vulnerability." [4]
        "Security researcher Mariusz Mlynski reported that an attacker able to
        convince a potential victim to set a new home page by dragging a link
        to the "home" button can set that user's home page to a javascript:
        URL. Once this is done the attacker's page can cause repeated crashes
        of the browser, eventually getting the script URL loaded in the
        privileged about:sessionrestore context." [5]
        "Mozilla community member Daniel Glazman of Disruptive Innovations
        reported a crash when accessing a keyframe's cssText after dynamic
        modification. This crash may be potentially exploitable." [6]
        "Mozilla developer Matt Brubeck reported that window.fullScreen is
        writeable by untrusted content now that the DOM fullscreen API is
        enabled. Because window.fullScreen does not include mozRequestFullscreen's
        security protections, it could be used for UI spoofing. This code
        change makes window.fullScreen read only by untrusted content, forcing
        the use of the DOM fullscreen API in normal usage." [7]
        "Mozilla developers identified and fixed several memory safety bugs in
        the browser engine used in Firefox and other Mozilla-based products.
        Some of these bugs 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.
        In general these flaws cannot be exploited through email in the
        Thunderbird and SeaMonkey products because scripting is disabled, but
        are potentially a risk in browser or browser-like contexts in those
        products." [8]


        Users of the affected versions should upgrade to the latest versions:
         - Firefox: 11, 10.0.3, or 3.6.28
         - Thunderbird: 11, 10.0.3, or 3.1.20
         - SeaMonkey: 2.8


        [1] Mozilla Foundation Security Advisory 2012-12

        [2] Mozilla Foundation Security Advisory 2012-13

        [3] Mozilla Foundation Security Advisory 2012-14

        [4] Mozilla Foundation Security Advisory 2012-15

        [5] Mozilla Foundation Security Advisory 2012-16

        [6] Mozilla Foundation Security Advisory 2012-17

        [7] Mozilla Foundation Security Advisory 2012-18

        [8] Mozilla Foundation Security Advisory 2012-19

AusCERT has made every effort to ensure that the information contained
in this document is accurate.  However, the decision to use the information
described is the responsibility of each user or organisation. The decision to
follow or act on information or advice contained in this security bulletin is
the responsibility of each user or organisation, and should be considered in
accordance with your organisation's site policies and procedures. AusCERT
takes no responsibility for consequences which may arise from following or
acting on information or advice contained in this security bulletin.

Australian Computer Emergency Response Team
The University of Queensland
Qld 4072

Internet Email:
Facsimile:      (07) 3365 7031
Telephone:      (07) 3365 4417 (International: +61 7 3365 4417)
                AusCERT personnel answer during Queensland business hours 
                which are GMT+10:00 (AEST).
                On call after hours for member emergencies only.