glsa-200703-08.xml


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200703-08">
  <title>SeaMonkey: Multiple vulnerabilities</title>
  <synopsis>
    Multiple vulnerabilities have been reported in SeaMonkey, some of which may
    allow user-assisted arbitrary remote code execution.
  </synopsis>
  <product type="ebuild">seamonkey</product>
  <announced>2007-03-09</announced>
  <revised count="01">2007-03-09</revised>
  <bug>165555</bug>
  <access>remote</access>
  <affected>
    <package name="www-client/seamonkey" auto="yes" arch="*">
      <unaffected range="ge">1.1.1</unaffected>
      <vulnerable range="lt">1.1.1</vulnerable>
    </package>
    <package name="www-client/seamonkey-bin" auto="yes" arch="*">
      <unaffected range="ge">1.1.1</unaffected>
      <vulnerable range="lt">1.1.1</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    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'.
    </p>
  </background>
  <description>
    <p>
    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.
    </p>
  </description>
  <impact type="normal">
    <p>
    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
    credentials.
    </p>
  </impact>
  <workaround>
    <p>
    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.
    </p>
  </workaround>
  <resolution>
    <p>
    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.
    </p>
    <p>
    All SeaMonkey users should upgrade to the latest version:
    </p>
    <code>
    # emerge --sync
    # emerge --ask --oneshot --verbose "&gt;=www-client/seamonkey-1.1.1"</code>
    <p>
    All SeaMonkey binary users should upgrade to the latest version:
    </p>
    <code>
    # emerge --sync
    # emerge --ask --oneshot --verbose "&gt;=www-client/seamonkey-bin-1.1.1"</code>
  </resolution>
  <references>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-6077">CVE-2006-6077</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0775">CVE-2007-0775</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0776">CVE-2007-0776</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0777">CVE-2007-0777</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0778">CVE-2007-0778</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0779">CVE-2007-0779</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0780">CVE-2007-0780</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0800">CVE-2007-0800</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0801">CVE-2007-0801</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0981">CVE-2007-0981</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0995">CVE-2007-0995</uri>
    <uri link="https://bugzilla.mozilla.org/show_bug.cgi?id=360493#c366">Mozilla Password Loss Bug</uri>
  </references>
  <metadata tag="submitter" timestamp="2007-03-04T00:05:48Z">
    falco
  </metadata>
  <metadata tag="bugReady" timestamp="2007-03-09T22:48:00Z">
    falco
  </metadata>
</glsa>