Vulnerability Note VU#783400
Mozilla Firefox URI filtering vulnerability
Mozilla Firefox does not filter input when sending certain URIs to registered protocol handlers. This may allow a remote, authenticated attacker to use Firefox as a vector for executing commands on a vulnerable system.
A Uniform Resource Identifier (URI) is a string of characters that can be used to identify a location, resource, or protocol. Mozilla Firefox will rely on Microsoft Windows to determine the appropriate protocol handler for certain URIs that it does not handle internally.
Firefox does not filter data passed to certain URI protocol handlers. This allows Firefox to be used as an attack vector for vulnerabilities in other applications. For example, Firefox can be used as an attack vector for the vulnerability in how Microsoft Windows itself determines the appropriate protocol handler [VU#403150]. Public exploit code for this vulnerability exists, which uses mailto, news, nntp, snews, and telnet URI handlers.
A remote, unauthenticated attacker may be able to execute arbitrary commands, using Firefox as an attack vector.
Mozilla has addressed this issue in Firefox 18.104.22.168.
Workarounds for administrators
Blocking mailto:%00, nntp:%00, news:%00, snews:%00, telnet:%00 strings inside of HTML pages or other network streams using an application layer firewall or IPS may mitigate this vulnerability. See the xs-sniper blog for more information about known vulnerable URIs. Please note that these filters may only work for the public exploit code that is currently available. Other variations of the exploit code can bypass these restrictions.
Systems Affected (Learn More)
|Vendor||Status||Date Notified||Date Updated|
|Mozilla||Affected||-||26 Jul 2007|
CVSS Metrics (Learn More)
This vulnerability was disclosed by Billy (BK) Rios.
This document was written by Ryan Giobbi, Jeff Gennari, and Will Dormann..
- CVE IDs: CVE-2007-3845
- Date Public: 25 Jul 2007
- Date First Published: 26 Jul 2007
- Date Last Updated: 31 Jul 2007
- Severity Metric: 25.51
- Document Revision: 36
If you have feedback, comments, or additional information about this vulnerability, please send us email.