[Full-disclosure] Google / GMail bug, all accounts vulnerable
coderman at gmail.com
Thu Dec 13 06:33:04 GMT 2007
On Dec 12, 2007 1:27 PM, Steven Adair <steven at securityzone.org> wrote:
> ... if you simply
> had a 302 or mod_rewrite rule for any image that you actually had written
> into the source of your page, you could achieve the same result.
no, that would only trigger a request when the page is loaded. a
refresh on the page is likely to get filtered, but that works too.
(and was used to implement an attack against Tor clients without entry
guards to good effect, for example.)
> Maybe the favicon.ico method is slightly transparent to the user as it's
> not present when you view the source.
the key difference of the favicon method (on fetchy ffoxes) is not
just the source, but the frequent repeated requests triggered by the
presence of a non-cached favicon. this is a versatile vector, as a
tainted favicon need only be viewable (not actually on that page, in
tabs, in bookmarks, etc) to trigger the requests.
> Explain to me what I am missing here.
perhaps you were expecting remote r00t in openbsd ip stack?
Full-Disclosure is hosted and sponsored by Secunia.