|
|||||||||||
|
RE: TRACE used to increase the dangerous of XSS.
From: Thor Larholm <thor(at)pivx.com>
Date: Thu Jan 23 2003 - 12:01:14 EST
Being able to send TRACE requests to the server is not an issue, unless you don't trust the client to see its own data. The XSS hole in your web application, which is needed in the first place to carry out this attack, is your problem - stealing the cookie or the basic-authentication headers through legitimate HTTP requests are just the symptoms, the side effects. It all comes down to what you trust the client to do in the first place. Being able to read a file from the victims machine after you have successfully abused a buffer overflow on it is not the problem, the buffer overflow is. It is impossible for the filesystem/webapplication to tell the difference between the legitimate requests coming from a client or the illegitimate requests being proxyed through the client by the attacker, and as such any restrictions will also restrict the legitimate requests. Comon practice in secure installations is to only allow the features that you need, instead of restricting those that you don't want. Typical targets such as online brokers and banks will most likely already have their webservers restricted to a few HTTP request types, since they by nature don't trust their clients. Thor
-----Original Message-----
So how do you propose fixing this issue? My solution is to remove TRACE support from XMLHTTP. Richard
-----Original Message-----
This is not a bug in IE or XMLHTTP, and the cookie is not returned as
part
IE is not the only browser that has XMLHTTP, Mozilla implemented a fullyworking copy with the exact same behavior. Neither remove any Set-Cookie HTTP headers from the response exposed to scripting.
Regards
Latest PivX research: Multi-vendor Game Server DDoS Vulnerability http://www.pivx.com/press_releases/mk_mk001.html
-----Original Message-----
Isn't this a bug in Internet Explorer? Shouldn't the Microsoft XMLHTTP ActiveX control be removing cookies from returned HTTP headers when a HTTP TRACE is done? I know that this already happens when a GET or a POST is done with XMLHTTP.
Richard M. Smith
This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 14:07:47 EDT |
||||||||||
|
|||||||||||