Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 229805 - CVE-2007-0775 Multiple Seamonkey flaws (CVE-2007-0777, CVE-2007-0995, CVE-2007-0996, CVE-2006-6077, CVE-2007-0778, CVE-2007-0779, CVE-2007-0780, CVE-2007-0800, CVE-2007-0008, CVE-2007-0009, CVE-2007-0981)
Summary: CVE-2007-0775 Multiple Seamonkey flaws (CVE-2007-0777, CVE-2007-0995, CVE-200...
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: seamonkey
Version: 4.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Gecko Maintainer
QA Contact: Ben Levenson
Whiteboard: impact=critical,source=mozilla,report...
Depends On:
TreeView+ depends on / blocked
Reported: 2007-02-23 16:25 UTC by Josh Bressers
Modified: 2007-11-30 22:07 UTC (History)
2 users (show)

Fixed In Version: RHSA-2007-0077
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-02-24 02:59:58 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2007:0077 0 normal SHIPPED_LIVE Critical: seamonkey security update 2007-03-13 15:30:13 UTC

Description Josh Bressers 2007-02-23 16:25:05 UTC
+++ This bug was initially created as a clone of Bug #229802 +++

The Mozilla project is releasing Seamonkey 1.0.8 to fix several flaws:


    Jesse Ruderman, Martijn Wargers and Olli Pettay reported crashes in the
    layout engine

    Brian Crowder, Igor Bukanov, Johnny Stenback, moz_bug_r_a4 and shutdown 
    reported potential memory corruption in the JavaScript engine


    The Mozilla parser formerly ignored invalid trailing characters in HTML tag 
    attribute names. This could in some cases be abused to evade web sites 
    content filters that attempted to remove problematic attributes, such as 
    event handlers, by matching against a regular expression that expected to 
    find trailing whitespace or one of a small set of delimiters.

    Stefan Esser demonstrated that this could be used for XSS attacks against
    sites that accept user content and do not specify the character set or 
    encoding used.

    MySpace users recently suffered a phishing attack where user-created content 
    included a login form that appeared to be a normal MySpace login, but was 
    altered to submit the data to an alternate site. Because the password form 
    appeared on a MySpace page the Firefox password manager filled in the saved 
    password, lending an air of legitimacy to the form.


    Aad reported that two web pages can collide in the disk cache with the 
    result that depending on order loaded the end of the longer document can be 
    appended to the shorter when the shorter is reloaded from the cache. It is 
    possible a determined hacker could construct a targeted attack to steal some 
    sensitive data from a particular web page (for example, transaction history 
    from a financial account). The potential victim would have to be already 
    logged into the targetted service (or be fooled into doing so) and then 
    visit the malicious site.


    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 hotspot property so that the visible 
    part of the cursor floated outside the browser content area.


    shutdown reported that if you could convince a user to open a blocked popup 
    you could perform a cross-site scripting attack against any site that 
    contains a frame whose source is a data: URL.

    Michal Zalewski reported that although pages loaded from the web normally 
    cannot open windows containing local files, if you could convince a user to 
    open a blocked popup then this restriction could be bypassed.


    CVE-2007-0008 CVE-2007-0009
    iDefense has informed Mozilla about two potential buffer overflow 
    vulnerabilities found by researcher regenrecht in the Network Security 
    Services (NSS) code for processing the SSLv2 protocol.


    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 

Comment 1 Josh Bressers 2007-02-23 21:25:27 UTC
These flaws are now public:

Comment 4 Red Hat Bugzilla 2007-02-24 02:59:59 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.