seamonkey was updated to version 1.1.18, fixing various security issues :

MFSA 2009-43 / CVE-2009-2404 Moxie Marlinspike reported a heap overflow vulnerability in the code that handles regular expressions in certificate names. This vulnerability could be used to compromise the browser and run arbitrary code by presenting a specially crafted certificate to the client. This code provided compatibility with the non-standard regular expression syntax historically supported by Netscape clients and servers. With version 3.5 Firefox switched to the more limited industry-standard wildcard syntax instead and is not vulnerable to this flaw. 

MFSA 2009-42 / CVE-2009-2408: IOActive security researcher Dan Kaminsky reported a mismatch in the treatment of domain names in SSL certificates between SSL clients and the Certificate Authorities (CA) which issue server certificates. In particular, if a malicious person requested a certificate for a host name with an invalid null character in it most CAs would issue the certificate if the requester owned the domain specified after the null, while most SSL clients (browsers) ignored that part of the name and used the unvalidated part in front of the null. This made it possible for attackers to obtain certificates that would function for any site they wished to target.
These certificates could be used to intercept and potentially alter encrypted communication between the client and a server such as sensitive bank account transactions. This vulnerability was independently reported to us by researcher Moxie Marlinspike who also noted that since Firefox relies on SSL to protect the integrity of security updates this attack could be used to serve malicious updates.
Mozilla would like to thank Dan and the Microsoft Vulnerability Research team for coordinating a multiple-vendor response to this problem.

The update also contains the fixes from the skipped 1.1.17 security update: MFSA 2009-17/CVE-2009-1307: Same-origin violations when Adobe Flash loaded via view-source: scheme 

MFSA 2009-21/CVE-2009-1311:POST data sent to wrong site when saving web page with embedded frame 

MFSA 2009-24/CVE-2009-1392/CVE-2009-1832/CVE-2009-1833: Crashes with evidence of memory corruption (rv:1.9.0.11) 

MFSA 2009-26/CVE-2009-1835: Arbitrary domain cookie access by local file: resources 

MFSA 2009-27/CVE-2009-1836: SSL tampering via non-200 responses to proxy CONNECT requests 

MFSA 2009-29/CVE-2009-1838: Arbitrary code execution using event listeners attached to an element whose owner document is null 

MFSA 2009-32/CVE-2009-1841: JavaScript chrome privilege escalation MFSA 2009-33/CVE-2009-2210: Crash viewing multipart/alternative message with text/enhanced part

Several flaws were found in the processing of malformed web content. A web page containing malicious content could cause SeaMonkey to crash or, potentially, execute arbitrary code as the user running SeaMonkey.
(CVE-2009-1392, CVE-2009-1833, CVE-2009-1838, CVE-2009-1841)

A flaw was found in the processing of malformed, local file content.
If a user loaded malicious, local content via the file:// URL, it was possible for that content to access other local data. (CVE-2009-1835)

After installing the update, SeaMonkey must be restarted for the changes to take effect.

The remote host is affected by the vulnerability described in GLSA-201301-01 (Mozilla Products: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in Mozilla Firefox,       Thunderbird, SeaMonkey, NSS, GNU IceCat, and XULRunner. Please review the       CVE identifiers referenced below for details.
  Impact :

    A remote attacker could entice a user to view a specially crafted web       page or email, possibly resulting in execution of arbitrary code or a       Denial of Service condition. Furthermore, a remote attacker may be able       to perform Man-in-the-Middle attacks, obtain sensitive information,       bypass restrictions and protection mechanisms, force file downloads,       conduct XML injection attacks, conduct XSS attacks, bypass the Same       Origin Policy, spoof URL&rsquo;s for phishing attacks, trigger a vertical       scroll, spoof the location bar, spoof an SSL indicator, modify the       browser&rsquo;s font, conduct clickjacking attacks, or have other unspecified       impact.
    A local attacker could gain escalated privileges, obtain sensitive       information, or replace an arbitrary downloaded file.
  Workaround :

    There is no known workaround at this time.

Versions of Firefox prior to 3.0.11 are affected by the following security issues : 

 - Multiple memory corruption vulnerabilities could potentially be exploited to execute arbitrary code. (MFSA 2009-24)
 - Certain invalid Unicode characters, when used as a part of IDN, can be displayed as a whitespace in the location bar. An attacker can exploit this vulnerability to spoof the location bar. (MFSA 2009-25)
 - It may be possible for local resources loaded via 'file: ' protocol to access any domain's cookies saved on a user's system. (MFSA 2009-26)
 - It may be possible to tamper with SSL date via non-200 responses to proxy CONNECT requests. (MFSA 2009-27)
 - A race condition exists in 'NPObjWrapper_NewResolve' when accessing the properties of a NPObject, a wrapped JSObject. (MFSA 2009-28)
 - If the owner document of an element becomes a null after garbage collection, then it may be possible to execute the event listeners within the wrong JavaScript context. An attacker can potentially exploit this vulnerability to execute arbitrary JavaScript with chrome privileges. (MFSA 2009-29)
 - When the 'file: ' resource is loaded from the location bar, the resource inherits principal of the previously loaded document. This could potentially allow unauthorized access to local files. (MFSA-2009-30)
 - While loading external scripts into XUL documents content-loading policies are not checked. (MFSA 2009-31)
 - It may also be possible for scripts from page content to run with elevated privileges. (MFSA 2009-32)

The remote host is running a version of SeaMonkey earlier than 1.1.17. Such versions are reportedly affected by multiple vulnerabilities : 

  - Multiple remote memory-corruption vulnerabilities.

  - Content injection vulnerabilities.

  - An information disclosure vulnerability.

  - A cross-site scripting vulnerability.

  - A privilege escalation vulnerability.

  - A security bypass vulnerability.

  - A URI spoofing vulnerability.

The installed version of Firefox is earlier than 3.0.11. Such versions are potentially affected by the following security issues : 

  - Multiple memory corruption vulnerabilities could potentially be exploited to execute arbitrary code. (MFSA 2009-24)

  - Certain invalid Unicode characters, when used as a part of IDN, can be displayed as a whitespace in the location bar. An attacker can exploit this vulnerability to spoof the location bar. (MFSA 2009-25)

  - It may be possible for local resources loaded via 'file: ' protocol to access any domain's cookies saved on a user's system. (MFSA 2009-26)

  - It may be possible to tamper with SSL date via non-200 responses to proxy CONNECT requests. (MFSA 2009-27)

  - A race condition exists in 'NPObjWrapper_NewResolve' when accessing the properties of a NPObject, a wrapped JSObject. (MFSA 2009-28)

  - If the owner document of an element becomes a null after garbage collection, then it may be possible to execute the event listeners within the wrong JavaScript context. An attacker can potentially exploit this vulnerability to execute arbitrary JavaScript with chrome privileges. (MFSA 2009-29)

  - When the 'file: ' resource is loaded from the location bar, the resource inherits principal of the previously loaded document. This could potentially allow unauthorized access to local files. (MFSA-2009-30)

  - While loading external scripts into XUL documents content-loading policies are not checked. (MFSA 2009-31)

  - It may also be possible for scripts from page content to run with elevated privileges. (MFSA 2009-32)

The remote host is running a version of Mozilla SeaMonkey earlier than 1.1.17. Such versions are reportedly affected by multiple vulnerabilities : 

  - Multiple remote memory-corruption vulnerabilities.

  - Content injection vulnerabilities.

  - An information disclosure vulnerability.

  - A cross-site scripting vulnerability.

  - A privilege escalation vulnerability.

  - A security bypass vulnerability.

  - A URI spoofing vulnerability.

ID	Name	Product	Family	Published	Updated	Severity
42327	openSUSE 10 Security Update : seamonkey (seamonkey-6538)	Nessus	SuSE Local Security Checks	10/30/2009	1/14/2021	high
60594	Scientific Linux Security Update : seamonkey on SL3.x, SL4.x i386/x86_64	Nessus	Scientific Linux Local Security Checks	8/1/2012	1/14/2021	high
63402	GLSA-201301-01 : Mozilla Products: Multiple vulnerabilities (BEAST)	Nessus	Gentoo Local Security Checks	1/8/2013	12/5/2022	critical
5072	Mozilla Firefox < 3.0.11 Multiple Vulnerabilities	Nessus Network Monitor	Web Clients	8/18/2004	3/6/2019	medium
5084	SeaMonkey < 1.1.17 Multiple Vulnerabilities	Nessus Network Monitor	Web Clients	8/18/2004	3/6/2019	medium
800755	Firefox < 3.0.11 Multiple Vulnerabilities	Log Correlation Engine	Web Clients			high
801255	Mozilla SeaMonkey < 1.1.17 Multiple Vulnerabilities	Log Correlation Engine	Web Clients			high

Detections

Analytics

Plugins Search

high

high

critical

medium

medium

high

high