Vulnerability Assessment & Network Security Forums
If through a vulnerability assessment, a network security issue is detected for the vulnerability below, applying the appropriate security patches in a timely matter is very important. If you have detected that your system has already been compromised, following CERT's Network Security recovery document will assist with recommended steps for system recovery.
Vulnerability Assessment Details
SeaMonkey: Multiple vulnerabilities
Detailed Explanation for this Vulnerability Assessment
The remote host is affected by the vulnerability described in GLSA-200701-04
(SeaMonkey: Multiple vulnerabilities)
An anonymous researcher found evidence of memory corruption in the way
SeaMonkey handles certain types of SVG comment DOM nodes. Georgi
Guninski and David Bienvenu discovered buffer overflows in the
processing of long "Content-Type:" and long non-ASCII MIME email
headers. Additionally, Frederik Reiss discovered a heap-based buffer
overflow in the conversion of a CSS cursor. Several other issues with
memory corruption were also fixed. SeaMonkey also contains less severe
malicious web page with a SeaMonkey application, possibly leading to
the execution of arbitrary code with the rights of the user running
those products. A possible hacker could also perform cross-site scripting
attacks, leading to the exposure of sensitive information, like user
disabled by default in the SeaMonkey email client, and enabling it is
There are no known workarounds for all the issues at this time.
All SeaMonkey users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=www-client/seamonkey-1.0.7"
Network Security Threat Level: High
Networks Security ID:
Vulnerability Assessment Copyright: (C) 2007 Michel Arboi
|Dell D620 Latitude Laptop 1.66GHZ C2D Dual Core CPU / 1GB Ram / 120GB HDD
|Intel Core i7-3770 3.4GHz Quad-Core (CM8063701211600) Processor
|AMD Turion Mobile Processor CPU TMRM72DAM22GG (en) 2.1GHZ
|AMD Ryzen 7 1700X 3.4GHz (3.8 Turbo) Eight Core (YD170XBCAEWOF) AM4 processor
No Discussions have been posted on this vulnerability.