|
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.
|