blob: 31246a8f7569a4f56eaced548e403cc6f28b8a89 [file] [log] [blame]
<?xml version="1.0" encoding="utf-8"?>
<glsa id="200703-08">
<title>SeaMonkey: Multiple vulnerabilities</title>
Multiple vulnerabilities have been reported in SeaMonkey, some of which may
allow user-assisted arbitrary remote code execution.
<product type="ebuild">seamonkey</product>
<announced>March 09, 2007</announced>
<revised>March 09, 2007: 01</revised>
<package name="www-client/seamonkey" auto="yes" arch="*">
<unaffected range="ge">1.1.1</unaffected>
<vulnerable range="lt">1.1.1</vulnerable>
<package name="www-client/seamonkey-bin" auto="yes" arch="*">
<unaffected range="ge">1.1.1</unaffected>
<vulnerable range="lt">1.1.1</vulnerable>
The SeaMonkey project is a community effort to deliver
production-quality releases of code derived from the application
formerly known as the 'Mozilla Application Suite'.
Tom Ferris reported a heap-based buffer overflow involving wide SVG
stroke widths that affects SeaMonkey. Various researchers reported some
errors in the JavaScript engine potentially leading to memory
corruption. SeaMonkey also contains minor vulnerabilities involving
cache collision and unsafe pop-up restrictions, filtering or CSS
rendering under certain conditions. All those vulnerabilities are the
same as in GLSA 200703-04 affecting Mozilla Firefox.
<impact type="normal">
An attacker could entice a user to view a specially crafted web page or
to read a specially crafted email that will trigger one of the
vulnerabilities, possibly leading to the execution of arbitrary code.
It is also possible for an attacker to spoof the address bar, steal
information through cache collision, bypass the local file protection
mechanism with pop-ups, or perform cross-site scripting attacks,
leading to the exposure of sensitive information, such as user
There is no known workaround at this time for all of these issues, but
most of them can be avoided by disabling JavaScript. Note that the
execution of JavaScript is disabled by default in the SeaMonkey email
client, and enabling it is strongly discouraged.
Users upgrading to the following release of SeaMonkey should note that
the corresponding Mozilla Firefox upgrade has been found to lose the
saved passwords file in some cases. The saved passwords are encrypted
and stored in the 'signons.txt' file of ~/.mozilla/ and we advise our
users to save that file before performing the upgrade.
All SeaMonkey users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose &quot;&gt;=www-client/seamonkey-1.1.1&quot;</code>
All SeaMonkey binary users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose &quot;&gt;=www-client/seamonkey-bin-1.1.1&quot;</code>
<uri link="">CVE-2006-6077</uri>
<uri link="">CVE-2007-0775</uri>
<uri link="">CVE-2007-0776</uri>
<uri link="">CVE-2007-0777</uri>
<uri link="">CVE-2007-0778</uri>
<uri link="">CVE-2007-0779</uri>
<uri link="">CVE-2007-0780</uri>
<uri link="">CVE-2007-0800</uri>
<uri link="">CVE-2007-0801</uri>
<uri link="">CVE-2007-0981</uri>
<uri link="">CVE-2007-0995</uri>
<uri link="">Mozilla Password Loss Bug</uri>
<metadata tag="submitter" timestamp="Sun, 04 Mar 2007 00:05:48 +0000">
<metadata tag="bugReady" timestamp="Fri, 09 Mar 2007 22:48:00 +0000">