Versions of SeaMonkey 2.0.x earlier than 2.0.9 are potentially affected by multiple vulnerabilities :
Multiple memory safety bugs could lead to memory corruption, potentially resulting in arbitrary code execution. (MFSA 2010-64)
By passing an excessively long string to βdocument.writeβ it may be possible to trigger a buffer overflow condition resulting in arbitrary code execution on the remote system. (MFSA 2010-65)
A use-after-free error in nsBarProp could allow arbitrary code execution on the remote system. (MFSA 2010-66)
A dangling pointer vulnerability in LookupGetterOrSetter could allow arbitrary code execution. (MFSA 2010-67)
The Gopher parser is affected by a cross-site scripting vulnerability. (MFSA 2010-68)
It is possible to steal information from a site in a different domain using modal calls. (MFSA 2010-69)
It is possible to establish a valid SSL connection to a remote host, provided the SSL certificate was created with a common name containing a wild card followed by the partial IP address of the remote host. (MFSA 2010-70)
A function used to load external libraries on the Windows platform could allow loading of unsafe DLLβs thus allowing binary planting attack. (MFSA 2010-71)
The SSL implementation allows servers to use Diffie-Hellman mode (DHE) with a very short key length. Such key lengths could be easily breakable with modern hardware. (MFSA 2010-72)
Binary data 801286.prm
.mozilla.org/security/announce/2010/mfsa2010-64.html
.mozilla.org/security/announce/2010/mfsa2010-65.html
.mozilla.org/security/announce/2010/mfsa2010-66.html
.mozilla.org/security/announce/2010/mfsa2010-67.html
.mozilla.org/security/announce/2010/mfsa2010-68.html
.mozilla.org/security/announce/2010/mfsa2010-69.html
.mozilla.org/security/announce/2010/mfsa2010-70.html
.mozilla.org/security/announce/2010/mfsa2010-71.html
.mozilla.org/security/announce/2010/mfsa2010-72.html
.mozilla.org/security/known-vulnerabilities/seamonkey20.html#seamonkey2.0.9
.westpoint.ltd.uk/advisories/wp-10-0001.txt
.zerodayinitiative.com/advisories/ZDI-10-219
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3170
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3173
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3174
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3175
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3176
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3177
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3178
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3179
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3180
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3181
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3182
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3183