Vulnerability Note VU#288308
Microsoft Internet Information Server (IIS) vulnerable to cross-site scripting via HTTP TRACK method
Microsoft Internet Information Server (IIS) servers support a HTTP method called TRACK. The HTTP TRACK method returns the contents of client HTTP requests in the entity-body of the TRACK response. This behavior could be leveraged by attackers to access sensitive information, such as cookies or authentication data, contained in the HTTP headers of the request.
Microsoft IIS servers support the HTTP TRACK method. The HTTP TRACK method asks a web server to echo the contents of the request back to the client for debugging purposes. The TRACK request is not RFC compliant and not well documented.
The complete request, including HTTP headers, is returned in the entity-body of a TRACK response. This leads to a Cross-site Scripting attack. Using features that provide client-side HTTP protocol support, such as XMLHTTP ActiveX or XMLDOM scripting objects, a web site can cause browsers to issue TRACK requests. The site can read the TRACK response, including sensitive header information such as cookies or authentication data.
Attackers may abuse HTTP TRACK functionality to gain access to information in HTTP headers such as cookies and authentication data. In the presence of other cross-domain vulnerabilities in web browsers, sensitive header information could be read from any domains that support the HTTP TRACK method.
Microsoft IIS 6 is reported to be not vulnerable. The TRACK method can be added to Microsoft's URLScan DenyVerbs section. It should not be in the AllowVerbs section in the urlscan.ini file.
Systems Affected (Learn More)
|Vendor||Status||Date Notified||Date Updated|
|Microsoft Corporation||Affected||-||05 Jan 2004|
CVSS Metrics (Learn More)
Thanks to Parcifal Aertssen for reporting this vulnerability.
This document was written by Jason A Rafail and Art Manion.
- CVE IDs: Unknown
- Date Public: 28 Dec 2003
- Date First Published: 05 Jan 2004
- Date Last Updated: 09 Jan 2004
- Document Revision: 9
If you have feedback, comments, or additional information about this vulnerability, please send us email.