172 matches found
openSUSE 10 Security Update : seamonkey (seamonkey-4596)
This update fixes several security issues in Mozilla SeaMonkey 1.0.9. Following security problems were fixed : - MFSA 2007-26 / CVE-2007-3844: Privilege escalation through chrome-loaded about:blank windows Mozilla researcher mozbugra4 reported that a flaw was introduced by the fix for MFSA 2007-2...
IE和Firefox浏览器Digest认证请求拆分漏洞
BUGTRAQ ID: 23668 CVECAN ID: CVE-2007-2292 IE和Firefox都是流行的WEB浏览器。 IE和Firefox在处理Digest认证方式时存在漏洞,可能导致验证失败。 如果用户使用Digest认证通过HTTP请求登录到网站的话,Firefox和IE可能无法正确地验证用户ID。恶意的网页可能在用户ID中包含有换行字符(%0a)注入头数据,如果用户通过代理进行连接的话代理就可能将认证请求解释为两个独立的请求,导致注入任意HTTP头。 Microsoft Internet Explorer 7.0.5730.11 Mozilla Thunderbird...
openSUSE 10 Security Update : seamonkey (seamonkey-2691)
This security update brings Mozilla SeaMonkey to version 1.1.1. http://www.mozilla.org/projects/security/known-vulnerabilities.html for more details. It includes fixes to the following security problems : - MFSA 2007-01: As part of the Firefox 2.0.0.2 and 1.5.0.10 update releases several bugs wer...
openSUSE 10 Security Update : seamonkey (seamonkey-3631)
This update brings Mozilla SeaMonkey to security update version 1.1.2 - MFSA 2007-17 / CVE-2007-2871 : Chris Thomas demonstrated that XUL popups opened by web content could be placed outside the boundaries of the content area. This could be used to spoof or hide parts of the browser chrome such a...
openSUSE 10 Security Update : seamonkey (seamonkey-3986)
This update fixes several security issues in Mozilla SeaMonkey 1.0.9. Following security problems were fixed : - MFSA 2007-18: Crashes with evidence of memory corruption The usual collection of stability fixes for crashes that look suspicious but haven't been proven to be exploitable. 25 were in...
openSUSE 10 Security Update : seamonkey (seamonkey-3984)
This update fixes several security issues in Mozilla SeaMonkey 1.1.3. Following security problems were fixed : - MFSA 2007-18: Crashes with evidence of memory corruption The usual collection of stability fixes for crashes that look suspicious but haven't been proven to be exploitable. 25 were in...
openSUSE 10 Security Update : seamonkey (seamonkey-2432)
This security update brings Mozilla SeaMonkey to version 1.0.7. http://www.mozilla.org/projects/security/known-vulnerabilities.html for more details. It includes fixes to the following security problems: CVE-2006-6497/MFSA2006-68: Crashes with evidence of memory corruption were fixed in the layou...
openSUSE 10 Security Update : seamonkey (seamonkey-2098)
This security update brings Mozilla SeaMonkey to version 1.0.5. Please also see http://www.mozilla.org/projects/security/known-vulnerabilities.html for more details. It includes fixes to the following security problems: MFSA 2006-64/CVE-2006-4571: Crashes with evidence of memory corruption MFSA...
openSUSE 10 Security Update : seamonkey (seamonkey-2811)
This security update brings Mozilla SeaMonkey to version 1.0.8. Please also see http://www.mozilla.org/projects/security/known-vulnerabilities.html for more details. It includes fixes to the following security problems : - MFSA 2007-01: As part of the Firefox 2.0.0.2 and 1.5.0.10 update releases...
openSUSE 10 Security Update : seamonkey (seamonkey-2250)
This security update brings Mozilla SeaMonkey to version 1.0.6. Please also see http://www.mozilla.org/projects/security/known-vulnerabilities.html for more details. It includes fixes to the following security problems: MFSA2006-65: Is split into 3 sub-entries, for ongoing stability improvements ...
SUSE-SA:2007:006: mozilla
The remote host is missing the patch for the advisory SUSE-SA:2007:006 mozilla. A number of security issues have been fixed in the Mozilla browser suite, which could be used by remote attackers to gain privileges, access to confidential information or cause denial of service attacks. Since the...
security flaw
The XULDocument.persist function in Mozilla, Firefox before 1.5.0.1, and SeaMonkey before 1.0 does not validate the attribute name, which allows remote attackers to execute arbitrary Javascript by injecting RDF data into the user's localstore.rdf file...