Updated SeaMonkey packages that fix security issues are now available for Red Hat Enterprise Linux 2.1, Red Hat Enterprise Linux 3, and Red Hat Enterprise Linux 4.

This update has been rated as having critical security impact by the Red Hat Security Response Team.

SeaMonkey is an open source Web browser, email and newsgroup client, IRC chat client, and HTML editor.

Several flaws were found in the processing of malformed web content. A web page containing malicious content could cause SeaMonkey to crash or, potentially, execute arbitrary code as the user running SeaMonkey.
(CVE-2008-5500, CVE-2008-5501, CVE-2008-5502, CVE-2008-5504, CVE-2008-5511, CVE-2008-5512, CVE-2008-5513)

Several flaws were found in the way malformed content was processed. A website containing specially crafted content could potentially trick a SeaMonkey user into surrendering sensitive information.
(CVE-2008-5503, CVE-2008-5506, CVE-2008-5507)

A flaw was found in the way malformed URLs were processed by SeaMonkey. This flaw could prevent various URL sanitization mechanisms from properly parsing a malicious URL. (CVE-2008-5508)

Note: after the errata packages are installed, SeaMonkey must be restarted for the update to take effect.

All SeaMonkey users should upgrade to these updated packages, which contain backported patches to resolve these issues.

The installed version of Firefox 3.0 is earlier than 3.0.5.  Such versions are potentially affected by the following security issues :

  - There are several stability bugs in the browser engine     that may lead to crashes with evidence of memory     corruption. (MFSA 2008-60)

  - The 'persist' attribute in XUL elements can be used to     store cookie-like information on a user's computer.
    (MFSA 2008-63)

  - Sensitive data may be disclosed in an XHR response when     an XMLHttpRequest is made to a same-origin resource,     which 302 redirects to a resource in a different     domain. (MFSA 2008-64)

  - A website may be able to access a limited amount of     data from a different domain by loading a same-domain     JavaScript URL that redirects to an off-domain target     resource containing data which is not parsable as     JavaScript. (MFSA 2008-65)

  - Errors arise when parsing URLs with leading whitespace     and control characters. (MFSA 2008-66)

  - An escaped null byte is ignored by the CSS parser and     treated as if it was not present in the CSS input     string. (MFSA 2008-67)

  - XSS and JavaScript privilege escalation are possible.
    (MFSA 2008-68)

  - XSS vulnerabilities in SessionStore may allow for     violating the browser's same-origin policy and     performing an XSS attack or running arbitrary     JavaScript with chrome privileges. (MFSA 2008-69)

  - Creating a Select object with a very large length can     result in memory exhaustion, causing a denial of     service. (CVE-2009-2535)

Update to the new upstream Firefox 3.0.5 / XULRunner 1.9.0.5 fixing multiple security issues: http://www.mozilla.org/security/known- vulnerabilities/firefox30.html#firefox3.0.5 This update also contains new builds of all applications depending on Gecko libraries, built against thenew version. Note: after the updated packages are installed, Firefox must be restarted for the update to take effect.

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Update to new upstream release 1.1.14 fixing multiple security issues:
http://www.mozilla.org/security/known- vulnerabilities/seamonkey11.html#seamonkey1.1.14

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Updated thunderbird packages that fix several security issues are now available for Red Hat Enterprise Linux 4 and 5.

This update has been rated as having moderate security impact by the Red Hat Security Response Team.

Mozilla Thunderbird is a standalone mail and newsgroup client.

Several flaws were found in the processing of malformed HTML mail content. An HTML mail message containing malicious content could cause Thunderbird to crash or, potentially, execute arbitrary code as the user running Thunderbird. (CVE-2008-5500, CVE-2008-5501, CVE-2008-5502, CVE-2008-5511, CVE-2008-5512, CVE-2008-5513)

Several flaws were found in the way malformed content was processed.
An HTML mail message containing specially crafted content could potentially trick a Thunderbird user into surrendering sensitive information. (CVE-2008-5503, CVE-2008-5506, CVE-2008-5507)

Note: JavaScript support is disabled by default in Thunderbird; the above issues are not exploitable unless JavaScript is enabled.

A flaw was found in the way malformed URLs were processed by Thunderbird. This flaw could prevent various URL sanitization mechanisms from properly parsing a malicious URL. (CVE-2008-5508)

All Thunderbird users should upgrade to these updated packages, which resolve these issues. All running instances of Thunderbird must be restarted for the update to take effect.

The Mozilla XULRunner 1.8.1 engine received backports for security problems in 1.9.0.5.

The following security issues were fixed :

  - Mozilla security researcher moz_bug_r_a4 reported that     an XBL binding, when attached to an unloaded document,     can be used to violate the same-origin policy and     execute arbitrary JavaScript within the context of a     different website. moz_bug_r_a4 also reported two     vulnerabilities by which page content can pollute     XPCNativeWrappers and run arbitary JavaScript with     chrome priviliges. Thunderbird shares the browser engine     with Firefox and could be vulnerable if JavaScript were     to be enabled in mail. This is not the default setting     and we strongly discourage users from running JavaScript     in mail. Workaround Disable JavaScript until a version     containing these fixes can be installed. (MFSA 2008-68 /     CVE-2008-5512 / CVE-2008-5511)

  - Kojima Hajime reported that unlike literal null     characters which were handled correctly, the escaped     form '\0' was ignored by the CSS parser and treated as     if it was not present in the CSS input string. This     issue could potentially be used to bypass script     sanitization routines in web applications. The severity     of this issue was determined to be low. (MFSA 2008-67 /     CVE-2008-5510)

  - Perl developer Chip Salzenberg reported that certain     control characters, when placed at the beginning of a     URL, would lead to incorrect parsing resulting in a     malformed URL being output by the parser. IBM     researchers Justin Schuh, Tom Cross, and Peter William     also reported a related symptom as part of their     research that resulted in MFSA 2008-37. There was no     direct security impact from this issue and its effect     was limited to the improper rendering of hyperlinks     containing specific characters. The severity of this     issue was determined to be low. (MFSA 2008-66 /     CVE-2008-5508)

  - Google security researcher Chris Evans reported that a     website could access a limited amount of data from a     different domain by loading a same-domain JavaScript URL     which redirects to an off-domain target resource     containing data which is not parsable as JavaScript.
    Upon attempting to load the data as JavaScript a syntax     error is generated that can reveal some of the file     context via the window.onerror DOM API. This issue could     be used by a malicious website to steal private data     from users who are authenticated on the redirected     website. How much data could be at risk would depend on     the format of the data and how the JavaScript parser     attempts to interpret it. For most files the amount of     data that can be recovered would be limited to the first     word or two. Some data files might allow deeper probing     with repeated loads. Thunderbird shares the browser     engine with Firefox and could be vulnerable if     JavaScript were to be enabled in mail. This is not the     default setting and we strongly discourage users from     running JavaScript in mail. Workaround Disable     JavaScript until a version containing these fixes can be     installed. (MFSA 2008-65 / CVE-2008-5507)

  - Marius Schilder of Google Security reported that when a     XMLHttpRequest is made to a same-origin resource which     302 redirects to a resource in a different domain, the     response from the cross-domain resource is readable by     the site issuing the XHR. Cookies marked HttpOnly were     not readable, but other potentially sensitive data could     be revealed in the XHR response including URL parameters     and content in the response body. Thunderbird shares the     browser engine with Firefox and could be vulnerable if     JavaScript were to be enabled in mail. This is not the     default setting and we strongly discourage users from     running JavaScript in mail. Workaround Disable     JavaScript until a version containing these fixes can be     installed. (MFSA 2008-64 / CVE-2008-5506)

  - Mozilla developer Boris Zbarsky reported that XBL     bindings could be used to read data from other domains,     a violation of the same-origin policy. The severity of     this issue was determined to be moderate due to several     mitigating factors: The target document requires a     <bindingsi> element in the XBL namespace in order to be     read. The reader of the data needs to know the id     attribute of the binding being read in advance. It is     unlikely that web services will expose private data in     the manner described above. Firefox 3 is not affected by     this issue. Thunderbird shares the browser engine with     Firefox and could be vulnerable if JavaScript were to be     enabled in mail. This is not the default setting and we     strongly discourage users from running JavaScript in     mail. Workaround Products built from the Mozilla 1.9.0     branch and later, Firefox 3 for example, are not     affected by this issue. Upgrading to one of these     products is a reliable workaround for this particular     issue and it is also Mozilla's recommendation that the     most current version of any Mozilla product be used.
    Alternatively, you can disable JavaScript until a     version containing these fixes can be installed. (MFSA     2008-61 / CVE-2008-5503)

  - Mozilla developers identified and fixed several     stability bugs in the browser engine used in Firefox and     other Mozilla-based products. Some of these crashes     showed evidence of memory corruption under certain     circumstances and we presume that with enough effort at     least some of these could be exploited to run arbitrary     code. Thunderbird shares the browser engine with Firefox     and could be vulnerable if JavaScript were to be enabled     in mail. This is not the default setting and we strongly     discourage users from running JavaScript in mail.
    Without further investigation we cannot rule out the     possibility that for some of these an attacker might be     able to prepare memory for exploitation through some     means other than JavaScript such as large images.
    Workaround Disable JavaScript until a version containing     these fixes can be installed. (MFSA 2008-60 /     CVE-2008-5500)

The Mozilla Thunderbird E-Mail client was updated to version 2.0.0.19.

The following security issues were fixed :

MFSA 2008-68 / CVE-2008-5512 / CVE-2008-5511: Mozilla security researcher moz_bug_r_a4 reported that an XBL binding, when attached to an unloaded document, can be used to violate the same-origin policy and execute arbitrary JavaScript within the context of a different website. moz_bug_r_a4 also reported two vulnerabilities by which page content can pollute XPCNativeWrappers and run arbitary JavaScript with chrome priviliges. Thunderbird shares the browser engine with Firefox and could be vulnerable if JavaScript were to be enabled in mail. This is not the default setting and we strongly discourage users from running JavaScript in mail. Workaround Disable JavaScript until a version containing these fixes can be installed.

MFSA 2008-67 / CVE-2008-5510: Kojima Hajime reported that unlike literal null characters which were handled correctly, the escaped form '\0' was ignored by the CSS parser and treated as if it was not present in the CSS input string. This issue could potentially be used to bypass script sanitization routines in web applications. The severity of this issue was determined to be low.

MFSA 2008-66 / CVE-2008-5508: Perl developer Chip Salzenberg reported that certain control characters, when placed at the beginning of a URL, would lead to incorrect parsing resulting in a malformed URL being output by the parser. IBM researchers Justin Schuh, Tom Cross, and Peter William also reported a related symptom as part of their research that resulted in MFSA 2008-37. There was no direct security impact from this issue and its effect was limited to the improper rendering of hyperlinks containing specific characters. The severity of this issue was determined to be low.

MFSA 2008-65 / CVE-2008-5507: Google security researcher Chris Evans reported that a website could access a limited amount of data from a different domain by loading a same-domain JavaScript URL which redirects to an off-domain target resource containing data which is not parsable as JavaScript. Upon attempting to load the data as JavaScript a syntax error is generated that can reveal some of the file context via the window.onerror DOM API. This issue could be used by a malicious website to steal private data from users who are authenticated on the redirected website. How much data could be at risk would depend on the format of the data and how the JavaScript parser attempts to interpret it. For most files the amount of data that can be recovered would be limited to the first word or two. Some data files might allow deeper probing with repeated loads. Thunderbird shares the browser engine with Firefox and could be vulnerable if JavaScript were to be enabled in mail. This is not the default setting and we strongly discourage users from running JavaScript in mail.
Workaround Disable JavaScript until a version containing these fixes can be installed.

MFSA 2008-64 / CVE-2008-5506: Marius Schilder of Google Security reported that when a XMLHttpRequest is made to a same-origin resource which 302 redirects to a resource in a different domain, the response from the cross-domain resource is readable by the site issuing the XHR. Cookies marked HttpOnly were not readable, but other potentially sensitive data could be revealed in the XHR response including URL parameters and content in the response body. Thunderbird shares the browser engine with Firefox and could be vulnerable if JavaScript were to be enabled in mail. This is not the default setting and we strongly discourage users from running JavaScript in mail. Workaround Disable JavaScript until a version containing these fixes can be installed.

MFSA 2008-61 / CVE-2008-5503: Mozilla developer Boris Zbarsky reported that XBL bindings could be used to read data from other domains, a violation of the same-origin policy. The severity of this issue was determined to be moderate due to several mitigating factors: The target document requires a <bindingsi> element in the XBL namespace in order to be read. The reader of the data needs to know the id attribute of the binding being read in advance. It is unlikely that web services will expose private data in the manner described above.
Firefox 3 is not affected by this issue. Thunderbird shares the browser engine with Firefox and could be vulnerable if JavaScript were to be enabled in mail. This is not the default setting and we strongly discourage users from running JavaScript in mail. Workaround Products built from the Mozilla 1.9.0 branch and later, Firefox 3 for example, are not affected by this issue. Upgrading to one of these products is a reliable workaround for this particular issue and it is also Mozilla's recommendation that the most current version of any Mozilla product be used. Alternatively, you can disable JavaScript until a version containing these fixes can be installed.

MFSA 2008-60 / CVE-2008-5500: Mozilla developers identified and fixed several stability bugs in the browser engine used in Firefox and other Mozilla-based products. Some of these crashes showed evidence of memory corruption under certain circumstances and we presume that with enough effort at least some of these could be exploited to run arbitrary code. Thunderbird shares the browser engine with Firefox and could be vulnerable if JavaScript were to be enabled in mail. This is not the default setting and we strongly discourage users from running JavaScript in mail. Without further investigation we cannot rule out the possibility that for some of these an attacker might be able to prepare memory for exploitation through some means other than JavaScript such as large images. Workaround Disable JavaScript until a version containing these fixes can be installed.

The Mozilla XULRunner 1.8.1 engine received backports for security problems in 1.9.0.5.

The following security issues were fixed :

MFSA 2008-68 / CVE-2008-5512 / CVE-2008-5511: Mozilla security researcher moz_bug_r_a4 reported that an XBL binding, when attached to an unloaded document, can be used to violate the same-origin policy and execute arbitrary JavaScript within the context of a different website. moz_bug_r_a4 also reported two vulnerabilities by which page content can pollute XPCNativeWrappers and run arbitary JavaScript with chrome priviliges. Thunderbird shares the browser engine with Firefox and could be vulnerable if JavaScript were to be enabled in mail. This is not the default setting and we strongly discourage users from running JavaScript in mail. Workaround Disable JavaScript until a version containing these fixes can be installed.

MFSA 2008-67 / CVE-2008-5510: Kojima Hajime reported that unlike literal null characters which were handled correctly, the escaped form '\0' was ignored by the CSS parser and treated as if it was not present in the CSS input string. This issue could potentially be used to bypass script sanitization routines in web applications. The severity of this issue was determined to be low.

MFSA 2008-66 / CVE-2008-5508: Perl developer Chip Salzenberg reported that certain control characters, when placed at the beginning of a URL, would lead to incorrect parsing resulting in a malformed URL being output by the parser. IBM researchers Justin Schuh, Tom Cross, and Peter William also reported a related symptom as part of their research that resulted in MFSA 2008-37. There was no direct security impact from this issue and its effect was limited to the improper rendering of hyperlinks containing specific characters. The severity of this issue was determined to be low.

MFSA 2008-65 / CVE-2008-5507: Google security researcher Chris Evans reported that a website could access a limited amount of data from a different domain by loading a same-domain JavaScript URL which redirects to an off-domain target resource containing data which is not parsable as JavaScript. Upon attempting to load the data as JavaScript a syntax error is generated that can reveal some of the file context via the window.onerror DOM API. This issue could be used by a malicious website to steal private data from users who are authenticated on the redirected website. How much data could be at risk would depend on the format of the data and how the JavaScript parser attempts to interpret it. For most files the amount of data that can be recovered would be limited to the first word or two. Some data files might allow deeper probing with repeated loads. Thunderbird shares the browser engine with Firefox and could be vulnerable if JavaScript were to be enabled in mail. This is not the default setting and we strongly discourage users from running JavaScript in mail.
Workaround Disable JavaScript until a version containing these fixes can be installed.

MFSA 2008-64 / CVE-2008-5506: Marius Schilder of Google Security reported that when a XMLHttpRequest is made to a same-origin resource which 302 redirects to a resource in a different domain, the response from the cross-domain resource is readable by the site issuing the XHR. Cookies marked HttpOnly were not readable, but other potentially sensitive data could be revealed in the XHR response including URL parameters and content in the response body. Thunderbird shares the browser engine with Firefox and could be vulnerable if JavaScript were to be enabled in mail. This is not the default setting and we strongly discourage users from running JavaScript in mail. Workaround Disable JavaScript until a version containing these fixes can be installed.

MFSA 2008-61 / CVE-2008-5503: Mozilla developer Boris Zbarsky reported that XBL bindings could be used to read data from other domains, a violation of the same-origin policy. The severity of this issue was determined to be moderate due to several mitigating factors: The target document requires a <bindingsi> element in the XBL namespace in order to be read. The reader of the data needs to know the id attribute of the binding being read in advance. It is unlikely that web services will expose private data in the manner described above.
Firefox 3 is not affected by this issue. Thunderbird shares the browser engine with Firefox and could be vulnerable if JavaScript were to be enabled in mail. This is not the default setting and we strongly discourage users from running JavaScript in mail. Workaround Products built from the Mozilla 1.9.0 branch and later, Firefox 3 for example, are not affected by this issue. Upgrading to one of these products is a reliable workaround for this particular issue and it is also Mozilla's recommendation that the most current version of any Mozilla product be used. Alternatively, you can disable JavaScript until a version containing these fixes can be installed.

MFSA 2008-60 / CVE-2008-5500: Mozilla developers identified and fixed several stability bugs in the browser engine used in Firefox and other Mozilla-based products. Some of these crashes showed evidence of memory corruption under certain circumstances and we presume that with enough effort at least some of these could be exploited to run arbitrary code. Thunderbird shares the browser engine with Firefox and could be vulnerable if JavaScript were to be enabled in mail. This is not the default setting and we strongly discourage users from running JavaScript in mail. Without further investigation we cannot rule out the possibility that for some of these an attacker might be able to prepare memory for exploitation through some means other than JavaScript such as large images. Workaround Disable JavaScript until a version containing these fixes can be installed.

The Mozilla XULRunner engine was updated to version 1.9.0.5.

The following security issues were fixed :

MFSA 2008-68 / CVE-2008-5512 / CVE-2008-5511: Mozilla security researcher moz_bug_r_a4 reported that an XBL binding, when attached to an unloaded document, can be used to violate the same-origin policy and execute arbitrary JavaScript within the context of a different website. moz_bug_r_a4 also reported two vulnerabilities by which page content can pollute XPCNativeWrappers and run arbitary JavaScript with chrome priviliges. Thunderbird shares the browser engine with Firefox and could be vulnerable if JavaScript were to be enabled in mail. This is not the default setting and we strongly discourage users from running JavaScript in mail. Workaround Disable JavaScript until a version containing these fixes can be installed.

MFSA 2008-67 / CVE-2008-5510: Kojima Hajime reported that unlike literal null characters which were handled correctly, the escaped form '\0' was ignored by the CSS parser and treated as if it was not present in the CSS input string. This issue could potentially be used to bypass script sanitization routines in web applications. The severity of this issue was determined to be low.

MFSA 2008-66 / CVE-2008-5508: Perl developer Chip Salzenberg reported that certain control characters, when placed at the beginning of a URL, would lead to incorrect parsing resulting in a malformed URL being output by the parser. IBM researchers Justin Schuh, Tom Cross, and Peter William also reported a related symptom as part of their research that resulted in MFSA 2008-37. There was no direct security impact from this issue and its effect was limited to the improper rendering of hyperlinks containing specific characters. The severity of this issue was determined to be low.

MFSA 2008-65 / CVE-2008-5507: Google security researcher Chris Evans reported that a website could access a limited amount of data from a different domain by loading a same-domain JavaScript URL which redirects to an off-domain target resource containing data which is not parsable as JavaScript. Upon attempting to load the data as JavaScript a syntax error is generated that can reveal some of the file context via the window.onerror DOM API. This issue could be used by a malicious website to steal private data from users who are authenticated on the redirected website. How much data could be at risk would depend on the format of the data and how the JavaScript parser attempts to interpret it. For most files the amount of data that can be recovered would be limited to the first word or two. Some data files might allow deeper probing with repeated loads. Thunderbird shares the browser engine with Firefox and could be vulnerable if JavaScript were to be enabled in mail. This is not the default setting and we strongly discourage users from running JavaScript in mail.
Workaround Disable JavaScript until a version containing these fixes can be installed.

MFSA 2008-64 / CVE-2008-5506: Marius Schilder of Google Security reported that when a XMLHttpRequest is made to a same-origin resource which 302 redirects to a resource in a different domain, the response from the cross-domain resource is readable by the site issuing the XHR. Cookies marked HttpOnly were not readable, but other potentially sensitive data could be revealed in the XHR response including URL parameters and content in the response body. Thunderbird shares the browser engine with Firefox and could be vulnerable if JavaScript were to be enabled in mail. This is not the default setting and we strongly discourage users from running JavaScript in mail. Workaround Disable JavaScript until a version containing these fixes can be installed.

MFSA 2008-61 / CVE-2008-5503: Mozilla developer Boris Zbarsky reported that XBL bindings could be used to read data from other domains, a violation of the same-origin policy. The severity of this issue was determined to be moderate due to several mitigating factors: The target document requires a <bindingsi> element in the XBL namespace in order to be read. The reader of the data needs to know the id attribute of the binding being read in advance. It is unlikely that web services will expose private data in the manner described above.
Firefox 3 is not affected by this issue. Thunderbird shares the browser engine with Firefox and could be vulnerable if JavaScript were to be enabled in mail. This is not the default setting and we strongly discourage users from running JavaScript in mail. Workaround Products built from the Mozilla 1.9.0 branch and later, Firefox 3 for example, are not affected by this issue. Upgrading to one of these products is a reliable workaround for this particular issue and it is also Mozilla's recommendation that the most current version of any Mozilla product be used. Alternatively, you can disable JavaScript until a version containing these fixes can be installed.

MFSA 2008-60 / CVE-2008-5500: Mozilla developers identified and fixed several stability bugs in the browser engine used in Firefox and other Mozilla-based products. Some of these crashes showed evidence of memory corruption under certain circumstances and we presume that with enough effort at least some of these could be exploited to run arbitrary code. Thunderbird shares the browser engine with Firefox and could be vulnerable if JavaScript were to be enabled in mail. This is not the default setting and we strongly discourage users from running JavaScript in mail. Without further investigation we cannot rule out the possibility that for some of these an attacker might be able to prepare memory for exploitation through some means other than JavaScript such as large images. Workaround Disable JavaScript until a version containing these fixes can be installed.

The version of Thunderbird installed on the remote Windows host is prior to 2.0.0.19. It is, therefore, affected by multiple vulnerabilities as referenced in the mfsa2008-68 advisory.

  - Multiple unspecified vulnerabilities in Mozilla Firefox 3.x before 3.0.5 and 2.x before 2.0.0.19,     Thunderbird 2.x before 2.0.0.19, and SeaMonkey 1.x before 1.1.14 allow remote attackers to run arbitrary     JavaScript with chrome privileges via unknown vectors in which page content can pollute     XPCNativeWrappers. (CVE-2008-5512)

  - Mozilla Firefox 3.x before 3.0.5 and 2.x before 2.0.0.19, Thunderbird 2.x before 2.0.0.19, and SeaMonkey     1.x before 1.1.14 allows remote attackers to bypass the same origin policy and conduct cross-site     scripting (XSS) attacks via an XBL binding to an unloaded document. (CVE-2008-5511)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
35192	RHEL 2.1 / 3 / 4 : seamonkey (RHSA-2008:1037)	Nessus	Red Hat Local Security Checks	2008/12/17	2021/1/14	critical
35219	Firefox 3.0.x < 3.0.5 Multiple Vulnerabilities	Nessus	Windows	2008/12/17	2026/6/23	high
35238	Fedora 9 : Miro-1.2.7-3.fc9 / blam-1.8.5-4.fc9.1 / cairo-dock-1.6.3.1-1.fc9.2 / chmsee-1.0.1-7.fc9 / etc (2008-11598)	Nessus	Fedora Local Security Checks	2008/12/21	2021/1/11	critical
38006	Fedora 10 : seamonkey-1.1.14-1.fc10 (2008-11490)	Nessus	Fedora Local Security Checks	2009/4/23	2021/1/11	critical
43722	CentOS 4 / 5 : thunderbird (CESA-2009:0002)	Nessus	CentOS Local Security Checks	2010/1/6	2021/1/4	critical
41504	SuSE 10 Security Update : Epiphany (ZYPP Patch Number 5889)	Nessus	SuSE Local Security Checks	2009/9/24	2021/1/14	critical
39895	openSUSE Security Update : MozillaThunderbird (MozillaThunderbird-401)	Nessus	SuSE Local Security Checks	2009/7/21	2021/1/14	critical
40073	openSUSE Security Update : mozilla-xulrunner181 (mozilla-xulrunner181-383)	Nessus	SuSE Local Security Checks	2009/7/21	2021/1/14	critical
40279	openSUSE Security Update : mozilla-xulrunner190 (mozilla-xulrunner190-382)	Nessus	SuSE Local Security Checks	2009/7/21	2021/1/14	critical
279184	Mozilla Thunderbird < 2.0.0.19	Nessus	Windows	2025/12/18	2025/12/18	medium

检测

插件搜索

critical

high

critical

critical

critical

critical

critical

critical

critical

medium