Mozilla Firefox before 1.5.0.5, Thunderbird before 1.5.0.5, and SeaMonkey before 1.0.3 allows remote attackers to reference remote files and possibly load chrome: URLs by tricking the user into copying or dragging links.

Updated firefox packages that fix several security bugs are now available for Red Hat Enterprise Linux 4. 

This update has been rated as having critical security impact by the Red Hat Security Response Team. 

Mozilla Firefox is an open source Web browser. 

Users of Firefox are advised to upgrade to these erratum packages, which contain Firefox version 1.5.0.8 that corrects these issues. 


From Red Hat Security Advisory 2006:0733 :

Several flaws were found in the way Firefox processes certain malformed Javascript code.  A malicious web page could cause the execution of Javascript code in such a way that could cause Firefox to crash or execute arbitrary code as the user running Firefox.  (CVE-2006-5463, CVE-2006-5747, CVE-2006-5748)

Several flaws were found in the way Firefox renders web pages.  A malicious web page could cause the browser to crash or possibly execute arbitrary code as the user running Firefox.  (CVE-2006-5464)

A flaw was found in the way Firefox verifies RSA signatures.  For RSA keys with exponent 3 it is possible for an attacker to forge a signature that would be incorrectly verified by the NSS library.  Firefox as shipped trusts several root Certificate Authorities that use exponent 3. An attacker could have created a carefully crafted SSL certificate which be incorrectly trusted when their site was visited by a victim.  This flaw was previously thought to be fixed in Firefox 1.5.0.7, however Ulrich Kuehn discovered the fix was incomplete (CVE-2006-5462)


From Red Hat Security Advisory 2006:0675 :

Two flaws were found in the way Firefox processed certain regular expressions.  A malicious web page could crash the browser or possibly execute arbitrary code as the user running Firefox.  (CVE-2006-4565, CVE-2006-4566)

A number of flaws were found in Firefox.  A malicious web page could crash the browser or possibly execute arbitrary code as the user running Firefox.  (CVE-2006-4571)

A flaw was found in the handling of Javascript timed events.  A malicious web page could crash the browser or possibly execute arbitrary code as the user running Firefox.  (CVE-2006-4253)

Daniel Bleichenbacher recently described an implementation error in RSA signature verification.  For RSA keys with exponent 3 it is possible for an attacker to forge a signature that would be incorrectly verified by the NSS library.  Firefox as shipped trusts several root Certificate Authorities that use exponent 3.  An attacker could have created a carefully crafted SSL certificate which be incorrectly trusted when their site was visited by a victim.  (CVE-2006-4340)

A flaw was found in the Firefox auto-update verification system.  An attacker who has the ability to spoof a victim's DNS could get Firefox to download and install malicious code.  In order to exploit this issue an attacker would also need to get a victim to previously accept an unverifiable certificate.  (CVE-2006-4567)

Firefox did not properly prevent a frame in one domain from injecting content into a sub-frame that belongs to another domain, which facilitates website spoofing and other attacks (CVE-2006-4568)

Firefox did not load manually opened, blocked popups in the right domain context, which could lead to cross-site scripting attacks.  In order to exploit this issue an attacker would need to find a site which would frame their malicious page and convince the user to manually open a blocked popup.  (CVE-2006-4569)


From Red Hat Security Advisory 2006:0610 :

The Mozilla Foundation has discontinued support for the Mozilla Firefox 1.0 branch.  This update deprecates the Mozilla Firefox 1.0 branch in Red Hat Enterprise Linux 4 in favor of the supported Mozilla Firefox 1.5 branch. 

This update also resolves a number of outstanding Firefox security issues :

Several flaws were found in the way Firefox processed certain javascript actions.  A malicious web page could execute arbitrary javascript instructions with the permissions of 'chrome', allowing the page to steal sensitive information or install browser malware.  (CVE-2006-2776, CVE-2006-2784, CVE-2006-2785, CVE-2006-2787, CVE-2006-3807, CVE-2006-3809, CVE-2006-3812)

Several denial of service flaws were found in the way Firefox processed certain web content.  A malicious web page could crash the browser or possibly execute arbitrary code as the user running Firefox. (CVE-2006-2779, CVE-2006-2780, CVE-2006-3801, CVE-2006-3677, CVE-2006-3113, CVE-2006-3803, CVE-2006-3805, CVE-2006-3806, CVE-2006-3811)

A cross-site scripting flaw was found in the way Firefox processed Unicode Byte-Order-Mark (BOM) markers in UTF-8 web pages.  A malicious web page could execute a script within the browser that a web input sanitizer could miss due to a malformed 'script' tag.  (CVE-2006-2783)

Several flaws were found in the way Firefox processed certain javascript actions.  A malicious web page could conduct a cross-site scripting attack or steal sensitive information (such as cookies owned by other domains).  (CVE-2006-3802, CVE-2006-3810)

A form file upload flaw was found in the way Firefox handled javascript input object mutation.  A malicious web page could upload an arbitrary local file at form submission time without user interaction. (CVE-2006-2782)

A denial of service flaw was found in the way Firefox called the crypto.signText() javascript function.  A malicious web page could crash the browser if the victim had a client certificate loaded. (CVE-2006-2778)

Two HTTP response smuggling flaws were found in the way Firefox processed certain invalid HTTP response headers.  A malicious web site could return specially crafted HTTP response headers which may bypass HTTP proxy restrictions.  (CVE-2006-2786)

A flaw was found in the way Firefox processed Proxy AutoConfig scripts. A malicious Proxy AutoConfig server could execute arbitrary javascript instructions with the permissions of 'chrome', allowing the page to steal sensitive information or install browser malware.  (CVE-2006-3808)

A double free flaw was found in the way the nsIX509::getRawDER method was called.  If a victim visited a carefully crafted web page, it was possible to execute arbitrary code as the user running Firefox. (CVE-2006-2788)

This security update brings Mozilla Firefox to version 1.5.0.6.

More details can be found on:
http://www.mozilla.org/projects/security/known-vulnerabiliti es.html

It includes fixes to the following security problems :

  - Code execution through deleted frame reference.
    (CVE-2006-3801 / MFSA 2006-44)

    Thilo Girmann discovered that in certain circumstances a     JavaScript reference to a frame or window was not     properly cleared when the referenced content went away,     and he demonstrated that this pointer to a deleted     object could be used to execute native code supplied by     the attacker.

  - JavaScript navigator Object Vulnerability.
    (CVE-2006-3677 / MFSA 2006-45)

    An anonymous researcher for TippingPoint and the Zero     Day Initiative showed that when used in a web page Java     would reference properties of the window.navigator     object as it started up. If the page replaced the     navigator object before starting Java then the browser     would crash in a way that could be exploited to run     native code supplied by the attacker.

  - Memory corruption with simultaneous events.
    (CVE-2006-3113 / MFSA 2006-46)

    Secunia Research has discovered a vulnerability in     Mozilla Firefox 1.5 branch, which can be exploited by     malicious people to compromise a user's system.

    The vulnerability is caused due to an memory corruption     error within the handling of simultaneously happening     XPCOM events, which leads to use of a deleted timer     object. This generally results in a crash but     potentially could be exploited to execute arbitrary code     on a user's system when a malicious website is visited.

  - Native DOM methods can be hijacked across domains.
    (CVE-2006-3802 / MFSA 2006-47)

    A malicious page can hijack native DOM methods on a     document object in another domain, which will run the     attacker's script when called by the victim page. This     could be used to steal login cookies, password, or other     sensitive data on the target page, or to perform actions     on behalf of a logged-in user.

    Access checks on all other properties and document nodes     are performed correctly. This cross-site scripting (XSS)     attack is limited to pages which use standard DOM     methods of the top-level document object, such as     document.getElementById(). This includes many popular     sites, especially the newer ones that offer rich     interaction to the user.

  - JavaScript new Function race condition. (CVE-2006-3803 /     MFSA 2006-48)

    H. D. Moore reported a testcase that was able to trigger     a race condition where JavaScript garbage collection     deleted a temporary variable still being used in the     creation of a new Function object. The resulting use of     a deleted object may be potentially exploitable to run     native code provided by the attacker.

  - Heap buffer overwrite on malformed VCard. (CVE-2006-3804     / MFSA 2006-49)

    A VCard attachment with a malformed base64 field (such     as a photo) can trigger a heap buffer overwrite. These     have proven exploitable in the past, though in this case     the overwrite is accompanied by an integer underflow     that would attempt to copy more data than the typical     machine has, leading to a crash.

  - JavaScript engine vulnerabilities. (CVE-2006-3805 /     CVE-2006-3806 / MFSA 2006-50)

    Continuing our security audit of the JavaScript engine,     Mozilla developers found and fixed several potential     vulnerabilities.

    Igor Bukanov and shutdown found additional places where     an untimely garbage collection could delete a temporary     object that was in active use (similar to MFSA 2006-01 /     MFSA 2006-10). Some of these may allow an attacker to     run arbitrary code given the right conditions.

    Georgi Guninski found potential integer overflow issues     with long strings in the toSource() methods of the     Object, Array and String objects as well as string     function arguments.

  - Privilege escalation using named-functions and redefined     'new Object()'. (CVE-2006-3807 / MFSA 2006-51)

    moz_bug_r_a4 discovered that named JavaScript functions     have a parent object created using the standard Object()     constructor (ECMA-specified behavior) and that this     constructor can be redefined by script (also     ECMA-specified behavior). If the Object() constructor is     changed to return a reference to a privileged object     with useful properties it is possible to have     attacker-supplied script excuted with elevated     privileges by calling the function. This could be used     to install malware or take other malicious actions.

    Our fix involves calling the internal Object constructor     which appears to be what other ECMA-compatible     interpreters do.

  - PAC privilege escalation using Function.prototype.call.
    (CVE-2006-3808 / MFSA 2006-52)

    moz_bug_r_a4 reports that a malicious Proxy AutoConfig     (PAC) server could serve a PAC script that can execute     code with elevated privileges by setting the required     FindProxyForURL function to the eval method on a     privileged object that leaked into the PAC sandbox. By     redirecting the victim to a specially crafted URL --     easily done since the PAC script controls which proxy to     use -- the URL 'hostname' can be executed as privileged     script.

    A malicious proxy server can perform spoofing attacks on     the user so it was already important to use a     trustworthy PAC server.

  - UniversalBrowserRead privilege escalation.
    (CVE-2006-3809 / MFSA 2006-53)

    shutdown reports that scripts granted the     UniversalBrowserRead privilege can leverage that into     the equivalent of the far more powerful     UniversalXPConnect since they are allowed to 'read' into     a privileged context. This allows the attacker the     ability to run scripts with the full privelege of the     user running the browser, possibly installing malware or     snooping on private data. This has been fixed so that     UniversalBrowserRead and UniversalBrowserWrite are     limited to reading from and writing into only     normally-privileged browser windows and frames.

  - XSS with XPCNativeWrapper(window).Function(...).
    (CVE-2006-3810 / MFSA 2006-54)

    shutdown reports that cross-site scripting (XSS) attacks     could be performed using the construct     XPCNativeWrapper(window).Function(...), which created a     function that appeared to belong to the window in     question even after it had been navigated to the target     site.

  - Crashes with evidence of memory corruption.
    (CVE-2006-3811 / MFSA 2006-55)

    As part of the Firefox 1.5.0.5 stability and security     release, developers in the Mozilla community looked for     and fixed several crash bugs to improve the stability of     Mozilla clients. Some of these crashes showed evidence     of memory corruption that we presume could be exploited     to run arbitrary code with enough effort.

  - chrome: scheme loading remote content. (CVE-2006-3812 /     MFSA 2006-56)

    Benjamin Smedberg discovered that chrome URL's could be     made to reference remote files, which would run scripts     with full privilege. There is no known way for web     content to successfully load a chrome: url, but if a     user could be convinced to do so manually (perhaps by     copying a link and pasting it into the location bar)     this could be exploited.

This update upgrades Thunderbird from 1.0.8 to 1.5.0.7. This step was necessary since the 1.0.x series is not supported by upstream any more.

Various flaws have been reported that allow an attacker to execute arbitrary code with user privileges by tricking the user into opening a malicious email containing JavaScript. Please note that JavaScript is disabled by default for emails, and it is not recommended to enable it. (CVE-2006-3113, CVE-2006-3802, CVE-2006-3803, CVE-2006-3805, CVE-2006-3806, CVE-2006-3807, CVE-2006-3809, CVE-2006-3810, CVE-2006-3811, CVE-2006-3812, CVE-2006-4253, CVE-2006-4565, CVE-2006-4566, CVE-2006-4571)

A buffer overflow has been discovered in the handling of .vcard files.
By tricking a user into importing a malicious vcard into his contacts, this could be exploited to execute arbitrary code with the user's privileges. (CVE-2006-3804)

The NSS library did not sufficiently check the padding of PKCS #1 v1.5 signatures if the exponent of the public key is 3 (which is widely used for CAs). This could be exploited to forge valid signatures without the need of the secret key. (CVE-2006-4340)

Jon Oberheide reported a way how a remote attacker could trick users into downloading arbitrary extensions with circumventing the normal SSL certificate check. The attacker would have to be in a position to spoof the victim's DNS, causing them to connect to sites of the attacker's choosing rather than the sites intended by the victim. If they gained that control and the victim accepted the attacker's cert for the Mozilla update site, then the next update check could be hijacked and redirected to the attacker's site without detection.
(CVE-2006-4567)

Georgi Guninski discovered that even with JavaScript disabled, a malicous email could still execute JavaScript when the message is viewed, replied to, or forwarded by putting the script in a remote XBL file loaded by the message. (CVE-2006-4570)

The 'enigmail' plugin and the translation packages have been updated to work with the new Thunderbird version.

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Various flaws have been reported that allow an attacker to execute arbitrary code with user privileges by tricking the user into opening a malicious email containing JavaScript. Please note that JavaScript is disabled by default for emails, and it is not recommended to enable it. (CVE-2006-3113, CVE-2006-3802, CVE-2006-3803, CVE-2006-3805, CVE-2006-3806, CVE-2006-3807, CVE-2006-3809, CVE-2006-3810, CVE-2006-3811, CVE-2006-3812)

A buffer overflow has been discovered in the handling of .vcard files.
By tricking a user into importing a malicious vcard into his contacts, this could be exploited to execute arbitrary code with the user's privileges. (CVE-2006-3084)

The 'enigmail' plugin has been updated to work with the new Thunderbird version.

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Various flaws have been reported that allow an attacker to execute arbitrary code with user privileges by tricking the user into opening a malicious URL. (CVE-2006-3113, CVE-2006-3677, CVE-2006-3801, CVE-2006-3803, CVE-2006-3805, CVE-2006-3806, CVE-2006-3807, CVE-2006-3809, CVE-2006-3811, CVE-2006-3812)

cross-site scripting vulnerabilities were found in the XPCNativeWrapper() function and native DOM method handlers. A malicious website could exploit these to modify the contents or steal confidential data (such as passwords) from other opened web pages.
(CVE-2006-3802, CVE-2006-3810)

A bug was found in the script handler for automatic proxy configuration. A malicious proxy could send scripts which could execute arbitrary code with the user's privileges. (CVE-2006-3808)

Please see 

http://www.mozilla.org/projects/security/known-vulnerabilities.html#Fi refox

for technical details of these vulnerabilities.

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

This security update brings Mozilla SeaMonkey to version 1.0.4.

Please also see http://www.mozilla.org/projects/security/known-vulnerabilities.html for more details.

It includes fixes to the following security problems :

  - CVE-2006-3801/MFSA 2006-44: Code execution through     deleted frame reference

    Thilo Girmann discovered that in certain circumstances a     JavaScript reference to a frame or window was not     properly cleared when the referenced content went away,     and he demonstrated that this pointer to a deleted     object could be used to execute native code supplied by     the attacker.

  - CVE-2006-3677/MFSA 2006-45: JavaScript navigator Object     Vulnerability

    An anonymous researcher for TippingPoint and the Zero     Day Initiative showed that when used in a web page Java     would reference properties of the window.navigator     object as it started up. If the page replaced the     navigator object before starting Java then the browser     would crash in a way that could be exploited to run     native code supplied by the attacker.

  - CVE-2006-3113/MFSA 2006-46: Memory corruption with     simultaneous events

    Secunia Research has discovered a vulnerability in     Mozilla Firefox 1.5 branch, which can be exploited by     malicious people to compromise a user's system.

    The vulnerability is caused due to an memory corruption     error within the handling of simultaneously happening     XPCOM events, which leads to use of a deleted timer     object. This generally results in a crash but     potentially could be exploited to execute arbitrary code     on a user's system when a malicious website is visited.

  - CVE-2006-3802/MFSA 2006-47: Native DOM methods can be     hijacked across domains

    A malicious page can hijack native DOM methods on a     document object in another domain, which will run the     attacker's script when called by the victim page. This     could be used to steal login cookies, password, or other     sensitive data on the target page, or to perform actions     on behalf of a logged-in user.

    Access checks on all other properties and document nodes     are performed correctly. This cross-site scripting (XSS)     attack is limited to pages which use standard DOM     methods of the top-level document object, such as     document.getElementById(). This includes many popular     sites, especially the newer ones that offer rich     interaction to the user.

  - CVE-2006-3803/MFSA 2006-48: JavaScript new Function race     condition

    H. D. Moore reported a testcase that was able to trigger     a race condition where JavaScript garbage collection     deleted a temporary variable still being used in the     creation of a new Function object. The resulting use of     a deleted object may be potentially exploitable to run     native code provided by the attacker.

  - CVE-2006-3804/MFSA 2006-49: Heap buffer overwrite on     malformed VCard

    A VCard attachment with a malformed base64 field (such     as a photo) can trigger a heap buffer overwrite. These     have proven exploitable in the past, though in this case     the overwrite is accompanied by an integer underflow     that would attempt to copy more data than the typical     machine has, leading to a crash.

  - CVE-2006-3806/MFSA 2006-50: JavaScript engine     vulnerabilities

    Continuing our security audit of the JavaScript engine,     Mozilla developers found and fixed several potential     vulnerabilities.

    Igor Bukanov and shutdown found additional places where     an untimely garbage collection could delete a temporary     object that was in active use (similar to MFSA 2006-01     and MFSA 2006-10). Some of these may allow an attacker     to run arbitrary code given the right conditions.

    Georgi Guninski found potential integer overflow issues     with long strings in the toSource() methods of the     Object, Array and String objects as well as string     function arguments.

  - CVE-2006-3807/MFSA 2006-51: Privilege escalation using     named-functions and redefined 'new Object()'

    moz_bug_r_a4 discovered that named JavaScript functions     have a parent object created using the standard Object()     constructor (ECMA-specified behavior) and that this     constructor can be redefined by script (also     ECMA-specified behavior). If the Object() constructor is     changed to return a reference to a privileged object     with useful properties it is possible to have     attacker-supplied script excuted with elevated     privileges by calling the function. This could be used     to install malware or take other malicious actions.

    Our fix involves calling the internal Object constructor     which appears to be what other ECMA-compatible     interpreters do.

  - CVE-2006-3808/MFSA 2006-52: PAC privilege escalation     using Function.prototype.call

    moz_bug_r_a4 reports that a malicious Proxy AutoConfig     (PAC) server could serve a PAC script that can execute     code with elevated privileges by setting the required     FindProxyForURL function to the eval method on a     privileged object that leaked into the PAC sandbox. By     redirecting the victim to a specially crafted URL --     easily done since the PAC script controls which proxy to     use -- the URL 'hostname' can be executed as privileged     script.

    A malicious proxy server can perform spoofing attacks on     the user so it was already important to use a     trustworthy PAC server.

  - CVE-2006-3809/MFSA 2006-53: UniversalBrowserRead     privilege escalation

    shutdown reports that scripts granted the     UniversalBrowserRead privilege can leverage that into     the equivalent of the far more powerful     UniversalXPConnect since they are allowed to 'read' into     a privileged context. This allows the attacker the     ability to run scripts with the full privelege of the     user running the browser, possibly installing malware or     snooping on private data. This has been fixed so that     UniversalBrowserRead and UniversalBrowserWrite are     limited to reading from and writing into only     normally-privileged browser windows and frames.

  - CVE-2006-3810/MFSA 2006-54: XSS with     XPCNativeWrapper(window).Function(...)

    shutdown reports that cross-site scripting (XSS) attacks     could be performed using the construct     XPCNativeWrapper(window).Function(...), which created a     function that appeared to belong to the window in     question even after it had been navigated to the target     site.

  - CVE-2006-3811/MFSA 2006-55: Crashes with evidence of     memory corruption

    As part of the Firefox 1.5.0.5 stability and security     release, developers in the Mozilla community looked for     and fixed several crash bugs to improve the stability of     Mozilla clients. Some of these crashes showed evidence     of memory corruption that we presume could be exploited     to run arbitrary code with enough effort.

  - CVE-2006-3812/MFSA 2006-56: chrome: scheme loading     remote content

    Benjamin Smedberg discovered that chrome URL's could be     made to reference remote files, which would run scripts     with full privilege. There is no known way for web     content to successfully load a chrome: url, but if a     user could be convinced to do so manually (perhaps by     copying a link and pasting it into the location bar)     this could be exploited.

This security update brings Mozilla Firefox to version 1.5.0.6.

Note that on SUSE Linux 9.2, 9.3 and 10.0 this is a major version upgrade, please check if your manually installed extensions and plugins are still working.

Please also see http://www.mozilla.org/projects/security/known-vulnerabilities.html for more details.

It includes fixes to the following security problems :

  - CVE-2006-3801/MFSA 2006-44: Code execution through     deleted frame reference

    Thilo Girmann discovered that in certain circumstances a     JavaScript reference to a frame or window was not     properly cleared when the referenced content went away,     and he demonstrated that this pointer to a deleted     object could be used to execute native code supplied by     the attacker.

  - CVE-2006-3677/MFSA 2006-45: JavaScript navigator Object     Vulnerability

    An anonymous researcher for TippingPoint and the Zero     Day Initiative showed that when used in a web page Java     would reference properties of the window.navigator     object as it started up. If the page replaced the     navigator object before starting Java then the browser     would crash in a way that could be exploited to run     native code supplied by the attacker.

  - CVE-2006-3113/MFSA 2006-46: Memory corruption with     simultaneous events

    Secunia Research has discovered a vulnerability in     Mozilla Firefox 1.5 branch, which can be exploited by     malicious people to compromise a user's system.

    The vulnerability is caused due to an memory corruption     error within the handling of simultaneously happening     XPCOM events, which leads to use of a deleted timer     object. This generally results in a crash but     potentially could be exploited to execute arbitrary code     on a user's system when a malicious website is visited.

  - CVE-2006-3802/MFSA 2006-47: Native DOM methods can be     hijacked across domains

    A malicious page can hijack native DOM methods on a     document object in another domain, which will run the     attacker's script when called by the victim page. This     could be used to steal login cookies, password, or other     sensitive data on the target page, or to perform actions     on behalf of a logged-in user.

    Access checks on all other properties and document nodes     are performed correctly. This cross-site scripting (XSS)     attack is limited to pages which use standard DOM     methods of the top-level document object, such as     document.getElementById(). This includes many popular     sites, especially the newer ones that offer rich     interaction to the user.

  - CVE-2006-3803/MFSA 2006-48: JavaScript new Function race     condition

    H. D. Moore reported a testcase that was able to trigger     a race condition where JavaScript garbage collection     deleted a temporary variable still being used in the     creation of a new Function object. The resulting use of     a deleted object may be potentially exploitable to run     native code provided by the attacker.

  - CVE-2006-3804/MFSA 2006-49: Heap buffer overwrite on     malformed VCard

    A VCard attachment with a malformed base64 field (such     as a photo) can trigger a heap buffer overwrite. These     have proven exploitable in the past, though in this case     the overwrite is accompanied by an integer underflow     that would attempt to copy more data than the typical     machine has, leading to a crash.

  - CVE-2006-3805/CVE-2006-3806/MFSA 2006-50: JavaScript     engine vulnerabilities

    Continuing our security audit of the JavaScript engine,     Mozilla developers found and fixed several potential     vulnerabilities.

    Igor Bukanov and shutdown found additional places where     an untimely garbage collection could delete a temporary     object that was in active use (similar to MFSA 2006-01     and MFSA 2006-10). Some of these may allow an attacker     to run arbitrary code given the right conditions.

    Georgi Guninski found potential integer overflow issues     with long strings in the toSource() methods of the     Object, Array and String objects as well as string     function arguments.

  - CVE-2006-3807/MFSA 2006-51: Privilege escalation using     named-functions and redefined 'new Object()'

    moz_bug_r_a4 discovered that named JavaScript functions     have a parent object created using the standard Object()     constructor (ECMA-specified behavior) and that this     constructor can be redefined by script (also     ECMA-specified behavior). If the Object() constructor is     changed to return a reference to a privileged object     with useful properties it is possible to have     attacker-supplied script excuted with elevated     privileges by calling the function. This could be used     to install malware or take other malicious actions.

    Our fix involves calling the internal Object constructor     which appears to be what other ECMA-compatible     interpreters do.

  - CVE-2006-3808/MFSA 2006-52: PAC privilege escalation     using Function.prototype.call

    moz_bug_r_a4 reports that a malicious Proxy AutoConfig     (PAC) server could serve a PAC script that can execute     code with elevated privileges by setting the required     FindProxyForURL function to the eval method on a     privileged object that leaked into the PAC sandbox. By     redirecting the victim to a specially crafted URL --     easily done since the PAC script controls which proxy to     use -- the URL 'hostname' can be executed as privileged     script.

    A malicious proxy server can perform spoofing attacks on     the user so it was already important to use a     trustworthy PAC server.

  - CVE-2006-3809/MFSA 2006-53: UniversalBrowserRead     privilege escalation

    shutdown reports that scripts granted the     UniversalBrowserRead privilege can leverage that into     the equivalent of the far more powerful     UniversalXPConnect since they are allowed to 'read' into     a privileged context. This allows the attacker the     ability to run scripts with the full privelege of the     user running the browser, possibly installing malware or     snooping on private data. This has been fixed so that     UniversalBrowserRead and UniversalBrowserWrite are     limited to reading from and writing into only     normally-privileged browser windows and frames.

  - CVE-2006-3810/MFSA 2006-54: XSS with     XPCNativeWrapper(window).Function(...)

    shutdown reports that cross-site scripting (XSS) attacks     could be performed using the construct     XPCNativeWrapper(window).Function(...), which created a     function that appeared to belong to the window in     question even after it had been navigated to the target     site.

  - CVE-2006-3811/MFSA 2006-55: Crashes with evidence of     memory corruption

    As part of the Firefox 1.5.0.5 stability and security     release, developers in the Mozilla community looked for     and fixed several crash bugs to improve the stability of     Mozilla clients. Some of these crashes showed evidence     of memory corruption that we presume could be exploited     to run arbitrary code with enough effort.

  - CVE-2006-3812/MFSA 2006-56: chrome: scheme loading     remote content

    Benjamin Smedberg discovered that chrome URL's could be     made to reference remote files, which would run scripts     with full privilege. There is no known way for web     content to successfully load a chrome: url, but if a     user could be convinced to do so manually (perhaps by     copying a link and pasting it into the location bar)     this could be exploited.

A number of security vulnerabilities have been discovered and corrected in the latest Mozilla Thunderbird program.

Corporate 3 had contained the Mozilla suite however, due to the support cycle for Mozilla, it was felt that upgrading Mozilla to Firefox and Thunderbird would allow for better future support for Corporate 3 users. To that end, the latest Thunderbird is being provided for Corporate 3 users which fix all known vulnerabilities up to version 1.5.0.5, as well as providing new and enhanced features.

Corporate users who were using Mozilla for mail may need to explicitly install the new mozilla-thunderbird packages.

For 2006 users, no explicit installs are necessary.

The following CVE names have been corrected with this update:
CVE-2006-2775, CVE-2006-2776, CVE-2006-2778, CVE-2006-2779, CVE-2006-2780, CVE-2006-2781, CVE-2006-2783, CVE-2006-2787, CVE-2006-3803, CVE-2006-3804, CVE-2006-3806, CVE-2006-3807, CVE-2006-3113, CVE-2006-3802, CVE-2006-3805, CVE-2006-3809, CVE-2006-3810, CVE-2006-3811, CVE-2006-3812.

A number of security vulnerabilities have been discovered and corrected in the latest Mozilla Firefox program.

Previous updates to Firefox were patch fixes to Firefox 1.0.6 that brought it in sync with 1.0.8 in terms of security fixes. In this update, Mozilla Firefox 1.5.0.6 is being provided which corrects a number of vulnerabilities that were previously unpatched, as well as providing new and enhanced features.

The following CVE names have been corrected with this update:
CVE-2006-2613, CVE-2006-2894, CVE-2006-2775, CVE-2006-2776, CVE-2006-2777, CVE-2006-2778, CVE-2006-2779, CVE-2006-2780, CVE-2006-2782, CVE-2006-2783, CVE-2006-2784, CVE-2006-2785, CVE-2006-2786, CVE-2006-2787, CVE-2006-2788, CVE-2006-3677, CVE-2006-3803, CVE-2006-3804, CVE-2006-3806, CVE-2006-3807, CVE-2006-3113, CVE-2006-3801, CVE-2006-3802, CVE-2006-3805, CVE-2006-3808, CVE-2006-3809, CVE-2006-3810, CVE-2006-3811, CVE-2006-3812.

Update :

The previous language packages were not correctly tagged for the new Firefox which resulted in many of them not loading properly. These updated language packages correct the problem.

Updated SeaMonkey packages that fix several security bugs in the mozilla packages are now available for Red Hat Enterprise Linux 2.1.

This update has been rated as having critical security impact by the Red Hat Security Response Team.

SeaMonkey is an open source Web browser, advanced email and newsgroup client, IRC chat client, and HTML editor.

The Mozilla Foundation has discontinued support for the Mozilla Suite.
This update deprecates the Mozilla Suite in Red Hat Enterprise Linux 2.1 in favor of the supported SeaMonkey Suite.

This update also resolves a number of outstanding Mozilla security issues :

Several flaws were found in the way SeaMonkey processed certain JavaScript actions. A malicious web page could execute arbitrary JavaScript instructions with the permissions of 'chrome', allowing the page to steal sensitive information or install browser malware.
(CVE-2006-2776, CVE-2006-2784, CVE-2006-2785, CVE-2006-2787, CVE-2006-3807, CVE-2006-3809, CVE-2006-3812)

Several denial of service flaws were found in the way SeaMonkey processed certain web content. A malicious web page could crash the browser or possibly execute arbitrary code as the user running SeaMonkey. (CVE-2006-2779, CVE-2006-2780, CVE-2006-3801, CVE-2006-3677, CVE-2006-3113, CVE-2006-3803, CVE-2006-3805, CVE-2006-3806, CVE-2006-3811)

Two flaws were found in the way SeaMonkey Messenger displayed malformed inline vcard attachments. If a victim viewed an email message containing a carefully crafted vcard it was possible to execute arbitrary code as the user running SeaMonkey Messenger.
(CVE-2006-2781, CVE-2006-3804)

A cross-site scripting flaw was found in the way SeaMonkey processed Unicode Byte-Order-Mark (BOM) markers in UTF-8 web pages. A malicious web page could execute a script within the browser that a web input sanitizer could miss due to a malformed 'script' tag. (CVE-2006-2783)

Several flaws were found in the way SeaMonkey processed certain JavaScript actions. A malicious web page could conduct a cross-site scripting attack or steal sensitive information (such as cookies owned by other domains). (CVE-2006-3802, CVE-2006-3810)

A form file upload flaw was found in the way SeaMonkey handled JavaScript input object mutation. A malicious web page could upload an arbitrary local file at form submission time without user interaction.
(CVE-2006-2782)

A denial of service flaw was found in the way SeaMonkey called the crypto.signText() JavaScript function. A malicious web page could crash the browser if the victim had a client certificate loaded.
(CVE-2006-2778)

Two HTTP response smuggling flaws were found in the way SeaMonkey processed certain invalid HTTP response headers. A malicious website could return specially crafted HTTP response headers which may bypass HTTP proxy restrictions. (CVE-2006-2786)

A flaw was found in the way SeaMonkey processed Proxy AutoConfig scripts. A malicious Proxy AutoConfig server could execute arbitrary JavaScript instructions with the permissions of 'chrome', allowing the page to steal sensitive information or install browser malware.
(CVE-2006-3808)

A double free flaw was found in the way the nsIX509::getRawDER method was called. If a victim visited a carefully crafted web page it was possible to execute arbitrary code as the user running SeaMonkey.
(CVE-2006-2788)

Users of Mozilla are advised to upgrade to this update, which contains SeaMonkey version 1.0.3 that corrects these issues.

Updated SeaMonkey packages that fix several security bugs in the mozilla package are now available for Red Hat Enterprise Linux 4.

This update has been rated as having critical security impact by the Red Hat Security Response Team.

SeaMonkey is an open source Web browser, advanced email and newsgroup client, IRC chat client, and HTML editor.

The Mozilla Foundation has discontinued support for the Mozilla Suite.
This update deprecates the Mozilla Suite in Red Hat Enterprise Linux 4 in favor of the supported SeaMonkey Suite.

This update also resolves a number of outstanding Mozilla security issues :

Several flaws were found in the way SeaMonkey processed certain JavaScript actions. A malicious web page could execute arbitrary JavaScript instructions with the permissions of 'chrome', allowing the page to steal sensitive information or install browser malware.
(CVE-2006-2776, CVE-2006-2784, CVE-2006-2785, CVE-2006-2787, CVE-2006-3807, CVE-2006-3809, CVE-2006-3812)

Several denial of service flaws were found in the way SeaMonkey processed certain web content. A malicious web page could crash the browser or possibly execute arbitrary code as the user running SeaMonkey. (CVE-2006-2779, CVE-2006-2780, CVE-2006-3801, CVE-2006-3677, CVE-2006-3113, CVE-2006-3803, CVE-2006-3805, CVE-2006-3806, CVE-2006-3811)

Two flaws were found in the way SeaMonkey-mail displayed malformed inline vcard attachments. If a victim viewed an email message containing a carefully crafted vcard it was possible to execute arbitrary code as the user running Mozilla-mail. (CVE-2006-2781, CVE-2006-3804)

A cross-site scripting flaw was found in the way SeaMonkey processed Unicode Byte-Order-Mark (BOM) markers in UTF-8 web pages. A malicious web page could execute a script within the browser that a web input sanitizer could miss due to a malformed 'script' tag. (CVE-2006-2783)

Several flaws were found in the way SeaMonkey processed certain JavaScript actions. A malicious web page could conduct a cross-site scripting attack or steal sensitive information (such as cookies owned by other domains). (CVE-2006-3802, CVE-2006-3810)

A form file upload flaw was found in the way SeaMonkey handled JavaScript input object mutation. A malicious web page could upload an arbitrary local file at form submission time without user interaction.
(CVE-2006-2782)

A denial of service flaw was found in the way SeaMonkey called the crypto.signText() JavaScript function. A malicious web page could crash the browser if the victim had a client certificate loaded.
(CVE-2006-2778)

Two HTTP response smuggling flaws were found in the way SeaMonkey processed certain invalid HTTP response headers. A malicious website could return specially crafted HTTP response headers which may bypass HTTP proxy restrictions. (CVE-2006-2786)

A flaw was found in the way SeaMonkey processed Proxy AutoConfig scripts. A malicious Proxy AutoConfig server could execute arbitrary JavaScript instructions with the permissions of 'chrome', allowing the page to steal sensitive information or install browser malware.
(CVE-2006-3808)

A double free flaw was found in the way the nsIX509::getRawDER method was called. If a victim visited a carefully crafted web page, it was possible to execute arbitrary code as the user running Mozilla.
(CVE-2006-2788)

Users of Mozilla are advised to upgrade to this update, which contains SeaMonkey version 1.0.3 that corrects these issues.

Updated SeaMonkey packages that fix several security bugs are now available for Red Hat Enterprise Linux 3.

This update has been rated as having critical security impact by the Red Hat Security Response Team.

SeaMonkey is an open source Web browser, advanced email and newsgroup client, IRC chat client, and HTML editor.

Several flaws were found in the way SeaMonkey processed certain JavaScript actions. A malicious web page could execute arbitrary JavaScript instructions with the permissions of 'chrome', allowing the page to steal sensitive information or install browser malware.
(CVE-2006-3807, CVE-2006-3809, CVE-2006-3812)

Several denial of service flaws were found in the way SeaMonkey processed certain web content. A malicious web page could crash the browser or possibly execute arbitrary code as the user running SeaMonkey. (CVE-2006-3801, CVE-2006-3677, CVE-2006-3113, CVE-2006-3803, CVE-2006-3805, CVE-2006-3806, CVE-2006-3811)

A buffer overflow flaw was found in the way SeaMonkey Messenger displayed malformed inline vcard attachments. If a victim viewed an email message containing a carefully crafted vcard, it was possible to execute arbitrary code as the user running SeaMonkey Messenger.
(CVE-2006-3804)

Several flaws were found in the way SeaMonkey processed certain JavaScript actions. A malicious web page could conduct a cross-site scripting attack or steal sensitive information (such as cookies owned by other domains). (CVE-2006-3802, CVE-2006-3810)

A flaw was found in the way SeaMonkey processed Proxy AutoConfig scripts. A malicious Proxy AutoConfig server could execute arbitrary JavaScript instructions with the permissions of 'chrome', allowing the page to steal sensitive information or install browser malware.
(CVE-2006-3808)

Users of SeaMonkey are advised to upgrade to this update, which contains SeaMonkey version 1.0.3 that corrects these issues.

The remote host is affected by the vulnerability described in GLSA-200608-04 (Mozilla Thunderbird: Multiple vulnerabilities)

    The following vulnerabilities have been reported:
    Benjamin Smedberg discovered that chrome URLss could be made to     reference remote files.
    Developers in the Mozilla community     looked for and fixed several crash bugs to improve the stability of     Mozilla clients.
    'shutdown' reports that cross-site scripting     (XSS) attacks could be performed using the construct     XPCNativeWrapper(window).Function(...), which created a function that     appeared to belong to the window in question even after it had been     navigated to the target site.
    'shutdown' reports that scripts     granting the UniversalBrowserRead privilege can leverage that into the     equivalent of the far more powerful UniversalXPConnect since they are     allowed to 'read' into a privileged context.
    'moz_bug_r_a4'     discovered that Named JavaScript functions have a parent object created     using the standard Object() constructor (ECMA-specified behavior) and     that this constructor can be redefined by script (also ECMA-specified     behavior).
    Igor Bukanov and shutdown found additional places     where an untimely garbage collection could delete a temporary object     that was in active use.
    Georgi Guninski found potential     integer overflow issues with long strings in the toSource() methods of     the Object, Array and String objects as well as string function     arguments.
    H. D. Moore reported a testcase that was able to     trigger a race condition where JavaScript garbage collection deleted a     temporary variable still being used in the creation of a new Function     object.
    A malicious page can hijack native DOM methods on a     document object in another domain, which will run the attacker's script     when called by the victim page.
    Secunia Research has     discovered a vulnerability which is caused due to an memory corruption     error within the handling of simultaneously happening XPCOM events.
    This leads to use of a deleted timer object.
  Impact :

    A user can be enticed to open specially crafted URLs, visit webpages     containing malicious JavaScript or execute a specially crafted script.
    These events could lead to the execution of arbitrary code, or the     installation of malware on the user's computer.
  Workaround :

    There is no known workaround at this time.

The remote host is affected by the vulnerability described in GLSA-200608-03 (Mozilla Firefox: Multiple vulnerabilities)

    The following vulnerabilities have been reported:
    Benjamin Smedberg discovered that chrome URL's could be made to     reference remote files.
    Developers in the Mozilla community     looked for and fixed several crash bugs to improve the stability of     Mozilla clients.
    'shutdown' reports that cross-site scripting     (XSS) attacks could be performed using the construct     XPCNativeWrapper(window).Function(...), which created a function that     appeared to belong to the window in question even after it had been     navigated to the target site.
    'shutdown' reports that scripts     granting the UniversalBrowserRead privilege can leverage that into the     equivalent of the far more powerful UniversalXPConnect since they are     allowed to 'read' into a privileged context.
    'moz_bug_r_a4'     reports that A malicious Proxy AutoConfig (PAC) server could serve a     PAC script that can execute code with elevated privileges by setting     the required FindProxyForURL function to the eval method on a     privileged object that leaked into the PAC sandbox.
    'moz_bug_r_a4' discovered that Named JavaScript functions have a     parent object created using the standard Object() constructor     (ECMA-specified behavior) and that this constructor can be redefined by     script (also ECMA-specified behavior).
    Igor Bukanov and     shutdown found additional places where an untimely garbage collection     could delete a temporary object that was in active use.
    Georgi     Guninski found potential integer overflow issues with long strings in     the toSource() methods of the Object, Array and String objects as well     as string function arguments.
    H. D. Moore reported a testcase     that was able to trigger a race condition where JavaScript garbage     collection deleted a temporary variable still being used in the     creation of a new Function object.
    A malicious page can hijack     native DOM methods on a document object in another domain, which will     run the attacker's script when called by the victim page.
    Secunia Research has discovered a vulnerability which is caused due     to an memory corruption error within the handling of simultaneously     happening XPCOM events. This leads to use of a deleted timer     object.
    An anonymous researcher for TippingPoint and the Zero     Day Initiative showed that when used in a web page Java would reference     properties of the window.navigator object as it started up.
    Thilo Girmann discovered that in certain circumstances a JavaScript     reference to a frame or window was not properly cleared when the     referenced content went away.
  Impact :

    A user can be enticed to open specially crafted URLs, visit webpages     containing malicious JavaScript or execute a specially crafted script.
    These events could lead to the execution of arbitrary code, or the     installation of malware on the user's computer.
  Workaround :

    There is no known workaround at this time.

The remote host is affected by the vulnerability described in GLSA-200608-02 (Mozilla SeaMonkey: Multiple vulnerabilities)

    The following vulnerabilities have been reported:
    Benjamin Smedberg discovered that chrome URL's could be made to     reference remote files.
    Developers in the Mozilla community     looked for and fixed several crash bugs to improve the stability of     Mozilla clients, which could lead to the execution of arbitrary code by     a remote attacker.
    'shutdown' reports that cross-site     scripting (XSS) attacks could be performed using the construct     XPCNativeWrapper(window).Function(...), which created a function that     appeared to belong to the window in question even after it had been     navigated to the target site.
    'shutdown' reports that scripts     granting the UniversalBrowserRead privilege can leverage that into the     equivalent of the far more powerful UniversalXPConnect since they are     allowed to 'read' into a privileged context.
    'moz_bug_r_a4'     reports that A malicious Proxy AutoConfig (PAC) server could serve a     PAC script that can execute code with elevated privileges by setting     the required FindProxyForURL function to the eval method on a     privileged object that leaked into the PAC sandbox.
    'moz_bug_r_a4' discovered that Named JavaScript functions have a     parent object created using the standard Object() constructor     (ECMA-specified behavior) and that this constructor can be redefined by     script (also ECMA-specified behavior).
    Igor Bukanov and     shutdown found additional places where an untimely garbage collection     could delete a temporary object that was in active use.
    Georgi     Guninski found potential integer overflow issues with long strings in     the toSource() methods of the Object, Array and String objects as well     as string function arguments.
    H. D. Moore reported a testcase     that was able to trigger a race condition where JavaScript garbage     collection deleted a temporary variable still being used in the     creation of a new Function object.
    A malicious page can hijack     native DOM methods on a document object in another domain, which will     run the attacker's script when called by the victim page.
    Secunia Research has discovered a vulnerability which is caused due     to an memory corruption error within the handling of simultaneously     happening XPCOM events. This leads to use of a deleted timer     object.
    An anonymous researcher for TippingPoint and the Zero     Day Initiative showed that when used in a web page Java would reference     properties of the window.navigator object as it started up.
    Thilo Girmann discovered that in certain circumstances a JavaScript     reference to a frame or window was not properly cleared when the     referenced content went away.
  Impact :

    A user can be enticed to open specially crafted URLs, visit webpages     containing malicious JavaScript or execute a specially crafted script.
    These events could lead to the execution of arbitrary code, or the     installation of malware on the user's computer.
  Workaround :

    There is no known workaround at this time.

Updated firefox packages that fix several security bugs are now available for Red Hat Enterprise Linux 4.

This update has been rated as having critical security impact by the Red Hat Security Response Team.

Mozilla Firefox is an open source Web browser.

The Mozilla Foundation has discontinued support for the Mozilla Firefox 1.0 branch. This update deprecates the Mozilla Firefox 1.0 branch in Red Hat Enterprise Linux 4 in favor of the supported Mozilla Firefox 1.5 branch.

This update also resolves a number of outstanding Firefox security issues :

Several flaws were found in the way Firefox processed certain JavaScript actions. A malicious web page could execute arbitrary JavaScript instructions with the permissions of 'chrome', allowing the page to steal sensitive information or install browser malware.
(CVE-2006-2776, CVE-2006-2784, CVE-2006-2785, CVE-2006-2787, CVE-2006-3807, CVE-2006-3809, CVE-2006-3812)

Several denial of service flaws were found in the way Firefox processed certain web content. A malicious web page could crash the browser or possibly execute arbitrary code as the user running Firefox. (CVE-2006-2779, CVE-2006-2780, CVE-2006-3801, CVE-2006-3677, CVE-2006-3113, CVE-2006-3803, CVE-2006-3805, CVE-2006-3806, CVE-2006-3811)

A cross-site scripting flaw was found in the way Firefox processed Unicode Byte-Order-Mark (BOM) markers in UTF-8 web pages. A malicious web page could execute a script within the browser that a web input sanitizer could miss due to a malformed 'script' tag. (CVE-2006-2783)

Several flaws were found in the way Firefox processed certain JavaScript actions. A malicious web page could conduct a cross-site scripting attack or steal sensitive information (such as cookies owned by other domains). (CVE-2006-3802, CVE-2006-3810)

A form file upload flaw was found in the way Firefox handled JavaScript input object mutation. A malicious web page could upload an arbitrary local file at form submission time without user interaction.
(CVE-2006-2782)

A denial of service flaw was found in the way Firefox called the crypto.signText() JavaScript function. A malicious web page could crash the browser if the victim had a client certificate loaded.
(CVE-2006-2778)

Two HTTP response smuggling flaws were found in the way Firefox processed certain invalid HTTP response headers. A malicious website could return specially crafted HTTP response headers which may bypass HTTP proxy restrictions. (CVE-2006-2786)

A flaw was found in the way Firefox processed Proxy AutoConfig scripts. A malicious Proxy AutoConfig server could execute arbitrary JavaScript instructions with the permissions of 'chrome', allowing the page to steal sensitive information or install browser malware.
(CVE-2006-3808)

A double free flaw was found in the way the nsIX509::getRawDER method was called. If a victim visited a carefully crafted web page, it was possible to execute arbitrary code as the user running Firefox.
(CVE-2006-2788)

Users of Firefox are advised to upgrade to this update, which contains Firefox version 1.5.0.5 that corrects these issues.

The remote Redhat Enterprise Linux 4 host has a package installed that is affected by multiple vulnerabilities as referenced in the RHSA-2006:0610 advisory.

    Mozilla Firefox is an open source Web browser.

    The Mozilla Foundation has discontinued support for the Mozilla Firefox     1.0 branch. This update deprecates the Mozilla Firefox 1.0 branch in     Red Hat Enterprise Linux 4 in favor of the supported Mozilla Firefox     1.5 branch.

    This update also resolves a number of outstanding Firefox security issues:

    Several flaws were found in the way Firefox processed certain javascript     actions. A malicious web page could execute arbitrary javascript     instructions with the permissions of chrome, allowing the page to steal     sensitive information or install browser malware. (CVE-2006-2776,     CVE-2006-2784, CVE-2006-2785, CVE-2006-2787, CVE-2006-3807, CVE-2006-3809,     CVE-2006-3812)

    Several denial of service flaws were found in the way Firefox processed     certain web content. A malicious web page could crash the browser or     possibly execute arbitrary code as the user running Firefox.
    (CVE-2006-2779, CVE-2006-2780, CVE-2006-3801, CVE-2006-3677, CVE-2006-3113,     CVE-2006-3803, CVE-2006-3805, CVE-2006-3806, CVE-2006-3811)

    A cross-site scripting flaw was found in the way Firefox processed     Unicode Byte-Order-Mark (BOM) markers in UTF-8 web pages. A malicious web     page could execute a script within the browser that a web input sanitizer     could miss due to a malformed script tag. (CVE-2006-2783)

    Several flaws were found in the way Firefox processed certain javascript     actions. A malicious web page could conduct a cross-site scripting attack     or steal sensitive information (such as cookies owned by other domains).
    (CVE-2006-3802, CVE-2006-3810)

    A form file upload flaw was found in the way Firefox handled javascript     input object mutation. A malicious web page could upload an arbitrary local     file at form submission time without user interaction. (CVE-2006-2782)

    A denial of service flaw was found in the way Firefox called the     crypto.signText() javascript function. A malicious web page could crash the     browser if the victim had a client certificate loaded. (CVE-2006-2778)

    Two HTTP response smuggling flaws were found in the way Firefox processed     certain invalid HTTP response headers. A malicious web site could return     specially crafted HTTP response headers which may bypass HTTP proxy     restrictions. (CVE-2006-2786)

    A flaw was found in the way Firefox processed Proxy AutoConfig scripts. A     malicious Proxy AutoConfig server could execute arbitrary javascript     instructions with the permissions of chrome, allowing the page to steal     sensitive information or install browser malware. (CVE-2006-3808)

    A double free flaw was found in the way the nsIX509::getRawDER method was     called. If a victim visited a carefully crafted web page, it was possible     to execute arbitrary code as the user running Firefox. (CVE-2006-2788)

    Users of Firefox are advised to upgrade to this update, which contains     Firefox version 1.5.0.5 that corrects these issues.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Versions of Mozilla Firefox 1.5.x prior to 1.5.0.5 are affected by various security issues, some of which may lead to execution of arbitrary code on the affected host subject to the user's privileges.

The remote Windows host contains a mail client that is affected by multiple vulnerabilities.  The remote version of Mozilla Thunderbird suffers from various security issues, at least one of which may lead to execution of arbitrary code on the affected host subject to the user's privileges.

A Mozilla Foundation Security Advisory reports of multiple issues.
Several of which can be used to run arbitrary code with the privilege of the user running the program.

- MFSA 2006-56 chrome: scheme loading remote content

- MFSA 2006-55 Crashes with evidence of memory corruption (rv:1.8.0.5)

- MFSA 2006-54 XSS with XPCNativeWrapper(window).Function(...)

- MFSA 2006-53 UniversalBrowserRead privilege escalation

- MFSA 2006-52 PAC privilege escalation using Function.prototype.call

- MFSA 2006-51 Privilege escalation using named-functions and redefined 'new Object()'

- MFSA 2006-50 JavaScript engine vulnerabilities

- MFSA 2006-49 Heap buffer overwrite on malformed VCard

- MFSA 2006-48 JavaScript new Function race condition

- MFSA 2006-47 Native DOM methods can be hijacked across domains

- MFSA 2006-46 Memory corruption with simultaneous events

- MFSA 2006-45 JavaScript navigator Object Vulnerability

- MFSA 2006-44 Code execution through deleted frame reference

The installed version of SeaMonkey contains various security issues, some of which could lead to execution of arbitrary code on the affected host subject to the user's privileges.

The installed version of Firefox is affected by various security issues, some of which may lead to execution of arbitrary code on the affected host subject to the user's privileges.

ID	Name	Product	Family	Severity
67422	Oracle Linux 4 : firefox (ELSA-2006-0733 / ELSA-2006-0675 / ELSA-2006-0610)	Nessus	Oracle Linux Local Security Checks	critical
29354	SuSE 10 Security Update : Firefox (ZYPP Patch Number 1960)	Nessus	SuSE Local Security Checks	high
27930	Ubuntu 5.10 : mozilla-thunderbird vulnerabilities (USN-350-1)	Nessus	Ubuntu Local Security Checks	critical
27908	Ubuntu 6.06 LTS : mozilla-thunderbird vulnerabilities (USN-329-1)	Nessus	Ubuntu Local Security Checks	critical
27905	Ubuntu 6.06 LTS : firefox vulnerabilities (USN-327-1)	Nessus	Ubuntu Local Security Checks	critical
27435	openSUSE 10 Security Update : seamonkey (seamonkey-1952)	Nessus	SuSE Local Security Checks	high
27113	openSUSE 10 Security Update : MozillaFirefox (MozillaFirefox-1981)	Nessus	SuSE Local Security Checks	high
23894	Mandrake Linux Security Advisory : mozilla-thunderbird (MDKSA-2006:146)	Nessus	Mandriva Local Security Checks	critical
23892	Mandrake Linux Security Advisory : mozilla-firefox (MDKSA-2006:143-1)	Nessus	Mandriva Local Security Checks	critical
22291	RHEL 2.1 : seamonkey (RHSA-2006:0594)	Nessus	Red Hat Local Security Checks	high
22163	CentOS 4 : seamonkey (CESA-2006:0609)	Nessus	CentOS Local Security Checks	high
22162	CentOS 3 : seamonkey (CESA-2006:0608)	Nessus	CentOS Local Security Checks	high
22150	RHEL 4 : seamonkey (RHSA-2006:0609)	Nessus	Red Hat Local Security Checks	high
22146	GLSA-200608-04 : Mozilla Thunderbird: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	high
22145	GLSA-200608-03 : Mozilla Firefox: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	high
22144	GLSA-200608-02 : Mozilla SeaMonkey: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	high
22137	CentOS 4 : Firefox (CESA-2006:0610)	Nessus	CentOS Local Security Checks	high
22121	RHEL 4 : firefox (RHSA-2006:0610)	Nessus	Red Hat Local Security Checks	medium
3695	Mozilla Firefox 1.5.x < 1.5.0.5 Multiple Vulnerabilities	Nessus Network Monitor	Web Clients	medium
3694	Mozilla Thunderbird < 1.5.0.5 Multiple Vulnerabilities (deprecated)	Nessus Network Monitor	SMTP Clients	medium
22114	RHEL 3 : seamonkey (RHSA-2006:0608)	Nessus	Red Hat Local Security Checks	high
22105	FreeBSD : mozilla -- multiple vulnerabilities (e2a92664-1d60-11db-88cf-000c6ec775d9)	Nessus	FreeBSD Local Security Checks	high
22097	SeaMonkey < 1.0.3 Multiple Vulnerabilities	Nessus	Windows	high
22095	Firefox < 1.5.0.5 Multiple Vulnerabilities	Nessus	Windows	high
801227	Mozilla Thunderbird < 1.5.0.5 Multiple Vulnerabilities	Log Correlation Engine	SMTP Clients	high
800763	Firefox < 1.5.0.5 Multiple Vulnerabilities	Log Correlation Engine	Web Clients	high

Detections

Analytics

CVE-2006-3812

critical

Tenable Plugins

critical

high

critical

critical

critical

high

high

critical

critical

high

high

high

high

high

high

high

high

medium

medium

medium

high

high

high

high

high

high