Overly broad permissions can turn one compromised account into a much larger security problem. Learn how to reduce unnecessary access, review privileges, and apply least privilege across modern Linux systems. Review Linux Privileges×

Alerts This Week
Warning Icon 1 461
Alerts This Week
Warning Icon 1 461

SciLinux 4.x: CVE-2010-3170 Critical SeaMonkey Security Flaws

Scientific Large Esm H446
Critical: seamonkey security update
Date: Wed, 20 Oct 2010 13:35:59 -0500
Reply-To: Troy Dawson 
Sender: Security Errata for Scientific Linux
 
From: Troy Dawson 
Subject: Security ERRATA Critical: seamonkey on SL4.x i386/x86_64
Comments: To: "This email address is being protected from spambots. You need JavaScript enabled to view it."
 

Synopsis:	Critical: seamonkey security update
Issue date:	2010-10-19
CVE Names:	CVE-2010-3170 CVE-2010-3173 CVE-2010-3176
 CVE-2010-3177 CVE-2010-3180 CVE-2010-3182

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 with the privileges of the user
running SeaMonkey. (CVE-2010-3176, CVE-2010-3180)

A flaw was found in the way the Gopher parser in SeaMonkey converted
text into HTML. A malformed file name on a Gopher server could, when
accessed by a victim running SeaMonkey, allow arbitrary JavaScript to be
executed in the context of the Gopher domain. (CVE-2010-3177)

A flaw was found in the script that launches SeaMonkey. The
LD_LIBRARY_PATH variable was appending a "." character, which could
allow a local attacker to execute arbitrary code with the privileges of
a different user running SeaMonkey, if that user ran SeaMonkey from
within an attacker-controlled directory. (CVE-2010-3182)

It was found that the SSL DHE (Diffie-Hellman Ephemeral) mode
implementation for key exchanges in SeaMonkey accepted DHE keys that
were 256 bits in length. This update removes support for 256 bit DHE
keys, as such keys are easily broken using modern hardware. (CVE-2010-3173)

A flaw was found in the way SeaMonkey matched SSL certificates when the
certificates had a Common Name containing a wildcard and a partial IP
address. SeaMonkey incorrectly accepted connections to IP addresses that
fell within the SSL certificate's wildcard range as valid SSL
connections, possibly allowing an attacker to conduct a
man-in-the-middle attack. (CVE-2010-3170)

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

SL 4.x

 SRPMS:
seamonkey-1.0.9-64.el4.src.rpm
 i386:
seamonkey-1.0.9-64.el4.i386.rpm
seamonkey-chat-1.0.9-64.el4.i386.rpm
seamonkey-devel-1.0.9-64.el4.i386.rpm
seamonkey-dom-inspector-1.0.9-64.el4.i386.rpm
seamonkey-js-debugger-1.0.9-64.el4.i386.rpm
seamonkey-mail-1.0.9-64.el4.i386.rpm
 x86_64:
seamonkey-1.0.9-64.el4.i386.rpm
seamonkey-1.0.9-64.el4.x86_64.rpm
seamonkey-chat-1.0.9-64.el4.i386.rpm
seamonkey-chat-1.0.9-64.el4.x86_64.rpm
seamonkey-devel-1.0.9-64.el4.x86_64.rpm
seamonkey-dom-inspector-1.0.9-64.el4.i386.rpm
seamonkey-dom-inspector-1.0.9-64.el4.x86_64.rpm
seamonkey-js-debugger-1.0.9-64.el4.i386.rpm
seamonkey-js-debugger-1.0.9-64.el4.x86_64.rpm
seamonkey-mail-1.0.9-64.el4.i386.rpm
seamonkey-mail-1.0.9-64.el4.x86_64.rpm

-Connie Sieh
-Troy Dawson