Vulnerabilidades Mozilla Suite y Firefox

Publicado por Dabo on abril 16, 2005
Seguridad Informática

Varias vulnerabilidades se han encontrado en los navegadores Mozilla , versiones 1.7.6 o anteriores y en Firefox versiones 1.0.2 y anteriores, el fallo más notable por el impacto que pueda causar es un posible ataque por Cross Site Scripting o ejecución remota de código por Websites maliciosos.
Hay solución a estos temas y os recomendamos actualizar a las nuevas versiones Mozilla Firefox 1.0.3  y  Mozilla 1.7.7  desde aquí.

Debajo del titular os pongo un detalle de las mismas

Detalle de las vulnerabilidades, fuente frsirt y Bugzilla

Nine vulnerabilities were identified in Mozilla Suite and Firefox, which may be exploited by malicious Websites to execute arbitrary commands or conduct Cross Site Scripting attacks.

– moz_bug_r_a4 reported several exploits giving an attacker the ability to install malicious code or steal data, requiring only that the user do commonplace actions like click on a link or open the context menu. The common cause in each case was privileged UI code (“chrome”) being overly trusting of DOM nodes from the content window.

– The native implementations of InstallTrigger and other XPInstall-related javascript objects did not properly validate that they were called on instances of the correct type. By passing other objects, even raw numbers, the javascript interpreter would jump to the wrong place in memory.

– Sites can use the _search target to open links in the Firefox sidebar. Two missing security checks allow malicious scripts to first open a privileged page (such as about:config) and then inject script using a javascript: url. This could be used to install malicious code or steal data without user interaction.

– A malicious search plugin could run javascript in the context of the displayed page each time a search is run. This could be used to conduct Cross Site Scripting attacks.

– Firefox and the Mozilla Suite support custom “favicons” through the tag. If a link tag is added to the page programmatically and a javascript: url is used, then script will run with elevated privileges and could run or install malicious software.

– A malicious script could define a setter function for a variable known to be used by a popular site, and if the user does browse to that site the malicious script will run in that page. This would allows the setter script to steal cookies or the contents of the page, or potentially perform actions on the user’s behalf (such as make purchases or delete webmail) depending heavily on how the site was designed.

– When a popup is blocked the user is given the ability to open that one popup through the popup-blocking status bar icon and, in Firefox, through the infobar. If the popup URL were javascript: selecting “Show javascript:…” from the infobar or popup blocking status bar icon menus would run the javascript with elevated privileges which could be used to install malicious software.

– When a webpage requires a plugin that is not installed the user can click to launch the Plugin Finder Service (PFS) to find an appropriate plugin. If the service does not have an appropriate plugin the EMBED tag is checked for a PLUGINSPAGE attribute, and if one is found the PFS dialog will contain a “manual install” button that will load the PLUGINSPAGE url. If the PLUGINSPAGE attribute contains a javascript: url then pressing the button could launch arbitrary code capable of stealing local data or installing malicious code.

– A bug in javascript’s regular expression string replacement when using an anonymous function as the replacement argument allows a malicious script to capture blocks of memory allocated to the browser. A web site could capture data and transmit it to a server without user interaction or knowledge (FrSIRT/ADV-2005-0312).

¿Quieres comentar algo sobre este post? Puedes hacerlo en nuestro foro de noticias.

Puedes seguir nuestras actualizaciones vía RSS, en Facebook y también desde Twitter.