A web browser on the remote host is affected by multiple
vulnerabilities.
Description :
The installed version of SeaMonkey is affected by various security
issues :
- A stability problem that could result in a crash during
JavaScript garbage collection (MFSA 2008-20).
- Several stability bugs leading to crashes which, in
some cases, show traces of memory corruption
(MFSA 2008-21).
- A vulnerability involving violation of the same-origin
policy could allow for cross-site scripting attacks
(MFSA 2008-22).
- JavaScript can be injected into the context of signed
JARs and executed under the context of the JARs signer
(MFSA 2008-23).
- By taking advantage of the privilege level stored in
the pre-compiled fastload file. an attacker may be
able to run arbitrary JavaScript code with chrome
privileges (MFSA 2008-24).
- Arbitrary code execution is possible in
mozIJSSubScriptLoader.loadSubScript() (MFSA 2008-25).
- Several function calls in the MIME handling code
use unsafe versions of string routines (MFSA 2008-26).
- An attacker can steal files from known locations on a
victims computer via originalTarget and DOM Range
(MFSA 2008-27).
- It is possible for a malicious Java applet to bypass
the same-origin policy and create arbitrary socket
connections to other domains (MFSA 2008-28).
- An improperly encoded .properties file in an add-on
can result in uninitialized memory being used, which
could lead to data formerly used by other programs
being exposed to the add-on code (MFSA 2008-29).
- File URLs in directory listings are not properly HTML-
escaped when the filenames contained particular
characters (MFSA 2008-30).
- A weakness in the trust model regarding alt names on
peer-trusted certs could lead to spoofing secure
connections to any other site (MFSA 2008-31).
- URL shortcut files on Windows (for example, saved IE
favorites) could be interpreted as if they were in the
local file context when opened by SeaMonkey, although
the referenced remote content would be downloaded and
displayed (MFSA 2008-32).
- A crash in Mozillas block reflow code could be used
by an attacker to crash the browser and run arbitrary
code on the victims computer (MFSA 2008-33).
