WebApp Sec mailing list archives

Re: [WEB SECURITY] Round-up: Ways to bypass HttpOnly (and HTTP Basic auth)


From: "Brian Eaton" <eaton.lists () gmail com>
Date: Wed, 3 May 2006 08:43:55 -0400

Bad form, replying to my own e-mail...

On 5/3/06, Brian Eaton <eaton.lists () gmail com> wrote:
> On the other hand, several attacks against the above techniques cropped up in the
> recent few years, and I'd like to summarize them in this message. All attacks assume
> an XSS condition in the application (actually, on the host for which the cookies/basic
> auth is used), and using this XSS condition, the data in the HttpOnly cookie/basic
> auth is read.

It looks like the attacks fall into three categories:

- attacks requiring XSS + TRACE.
- attacks requiring XSS + request smuggling.
- attacks requiring XSS + a test script that acts similarly to the
TRACE method, returning request values to the browser.

There's one other class of attacks that HttpOnly doesn't help with,
CSRF.  Note that XSS is not a prerequisite to CSRF, but if the
application is vulnerable to XSS it is probably vulnerable to CSRF as
well.

Comment 20 to the mozilla bug describes the attack.

https://bugzilla.mozilla.org/show_bug.cgi?id=178993#c20

Regards,
Brian

-------------------------------------------------------------------------
Sponsored by: Watchfire

The Twelve Most Common Application-level Hack Attacks
Hackers continue to add billions to the cost of doing business online
despite security executives' efforts to prevent malicious attacks. This
whitepaper identifies the most common methods of attacks that we have seen,
and outlines a guideline for developing secure web applications.
Download this whitepaper today!

https://www.watchfire.com/securearea/whitepapers.aspx?id=701300000007t9r
--------------------------------------------------------------------------


Current thread: