Info

Last Modified

2 months ago

Percent Complete

100%

Disclosure

Dec 27, 2003

Discovery

Jan 02, 2003

Dates

Exploit

Dec 27, 2003

Solution

Unknown

Description

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. Attackers may abuse HTTP TRACK functionality to gain access to information in HTTP headers that is not otherwise available via the DOM interface. Examples of such information are cookies and authentication data. In the presence of other cross-site domain vulnerabilities in web browsers, sensitive header information could be read from domains other than the target of the HTTP TRACK request.

Classification

Location: Remote/Network Access Required
Attack Type: Information Disclosure
Impact: Loss of Confidentiality
Exploit: Exploit Available
Disclosure: OSVDB Verified

Technical

In the indicated versions, the TRACK request is not logged. It can be used to create much traffic, making it available for DDoS amplification. A more important issue with a TRACK request is cross-site tracing: a malicious web page or e-mail can send a TRACE/TRACK request to another website (using client-side HTTP support). Using features 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. This extends to html e-mail in clients that support such features.

The Apache web server can also be configured to echo TRACK requests back to the user. However, by default Apache servers are not configured that way. Also, the default workaround for the TRACK method is to configure the server using the same tools one would use to implement the TRACK method.

IIS on the other hand, does answer TRACK requests as designed by default. In addition, an executable must be added to vulnerable versions to avoid exposing the server to this attack. This executable is not included on default original media. You must download it from the supplier.

Solution

Based on your site requirements and policy, you should consider disabling HTTP TRACK support in your web server. For Apache web servers, use the Apache mod_rewrite module to deny HTTP TRACK requests or to permit only the methods needed to meet site requirements and policy. For Microsoft's Internet Information Service (IIS), download the URLScan tool from Microsoft to deny HTTP TRACK requests or to permit only the methods needed to meet site requirements and policy. Upgrade to the latest version of Microsoft IIS (6.0 or later), available from the Microsoft Web site. For other web servers, consult your documentation for details.