New! Plugin Severity Now Using CVSS v3
The calculated severity for Plugins has been updated to use CVSS v3 by default. Plugins that do not have a CVSS v3 score will fall back to CVSS v2 for calculating severity. Severity display preferences can be toggled in the settings dropdown.
SynopsisThe remote SuSE 10 host is missing a security-related patch.
DescriptionThis security update brings Mozilla Firefox to version 18.104.22.168.
More details can be found on:
It includes fixes to the following security problems :
- Code execution through deleted frame reference.
(CVE-2006-3801 / MFSA 2006-44)
(CVE-2006-3677 / MFSA 2006-45)
An anonymous researcher for TippingPoint and the Zero Day Initiative showed that when used in a web page Java would reference properties of the window.navigator object as it started up. If the page replaced the navigator object before starting Java then the browser would crash in a way that could be exploited to run native code supplied by the attacker.
- Memory corruption with simultaneous events.
(CVE-2006-3113 / MFSA 2006-46)
Secunia Research has discovered a vulnerability in Mozilla Firefox 1.5 branch, which can be exploited by malicious people to compromise a user's system.
The vulnerability is caused due to an memory corruption error within the handling of simultaneously happening XPCOM events, which leads to use of a deleted timer object. This generally results in a crash but potentially could be exploited to execute arbitrary code on a user's system when a malicious website is visited.
- Native DOM methods can be hijacked across domains.
(CVE-2006-3802 / MFSA 2006-47)
A malicious page can hijack native DOM methods on a document object in another domain, which will run the attacker's script when called by the victim page. This could be used to steal login cookies, password, or other sensitive data on the target page, or to perform actions on behalf of a logged-in user.
Access checks on all other properties and document nodes are performed correctly. This cross-site scripting (XSS) attack is limited to pages which use standard DOM methods of the top-level document object, such as document.getElementById(). This includes many popular sites, especially the newer ones that offer rich interaction to the user.
- Heap buffer overwrite on malformed VCard. (CVE-2006-3804 / MFSA 2006-49)
A VCard attachment with a malformed base64 field (such as a photo) can trigger a heap buffer overwrite. These have proven exploitable in the past, though in this case the overwrite is accompanied by an integer underflow that would attempt to copy more data than the typical machine has, leading to a crash.
Igor Bukanov and shutdown found additional places where an untimely garbage collection could delete a temporary object that was in active use (similar to MFSA 2006-01 / MFSA 2006-10). Some of these may allow an attacker to run arbitrary code given the right conditions.
Georgi Guninski found potential integer overflow issues with long strings in the toSource() methods of the Object, Array and String objects as well as string function arguments.
- Privilege escalation using named-functions and redefined 'new Object()'. (CVE-2006-3807 / MFSA 2006-51)
Our fix involves calling the internal Object constructor which appears to be what other ECMA-compatible interpreters do.
- PAC privilege escalation using Function.prototype.call.
(CVE-2006-3808 / MFSA 2006-52)
moz_bug_r_a4 reports that a malicious Proxy AutoConfig (PAC) server could serve a PAC script that can execute code with elevated privileges by setting the required FindProxyForURL function to the eval method on a privileged object that leaked into the PAC sandbox. By redirecting the victim to a specially crafted URL -- easily done since the PAC script controls which proxy to use -- the URL 'hostname' can be executed as privileged script.
A malicious proxy server can perform spoofing attacks on the user so it was already important to use a trustworthy PAC server.
- UniversalBrowserRead privilege escalation.
(CVE-2006-3809 / MFSA 2006-53)
shutdown reports that scripts granted the UniversalBrowserRead privilege can leverage that into the equivalent of the far more powerful UniversalXPConnect since they are allowed to 'read' into a privileged context. This allows the attacker the ability to run scripts with the full privelege of the user running the browser, possibly installing malware or snooping on private data. This has been fixed so that UniversalBrowserRead and UniversalBrowserWrite are limited to reading from and writing into only normally-privileged browser windows and frames.
- XSS with XPCNativeWrapper(window).Function(...).
(CVE-2006-3810 / MFSA 2006-54)
shutdown reports that cross-site scripting (XSS) attacks could be performed using the construct XPCNativeWrapper(window).Function(...), which created a function that appeared to belong to the window in question even after it had been navigated to the target site.
- Crashes with evidence of memory corruption.
(CVE-2006-3811 / MFSA 2006-55)
As part of the Firefox 22.214.171.124 stability and security release, developers in the Mozilla community looked for and fixed several crash bugs to improve the stability of Mozilla clients. Some of these crashes showed evidence of memory corruption that we presume could be exploited to run arbitrary code with enough effort.
- chrome: scheme loading remote content. (CVE-2006-3812 / MFSA 2006-56)
Benjamin Smedberg discovered that chrome URL's could be made to reference remote files, which would run scripts with full privilege. There is no known way for web content to successfully load a chrome: url, but if a user could be convinced to do so manually (perhaps by copying a link and pasting it into the location bar) this could be exploited.
SolutionApply ZYPP patch number 1960.