This vuln is not exploitable in this condition against IIS server 6
and possibly earlier versions. IIS will die on the null character in
the new request. It doesn't seem like anyone has brought up this
fact.
Example (IIS): location.hostname='microsoft.com\x00www.coredump.cx';
Output:
microsoft.com returns '400 Bad Request.'.
Any input would be appreciated until the obvious patch comes out.
Regards,
base
On 2/15/07, pdp (architect) <pdp.gnucitizen@googlemail.com> wrote:
weird, firefox slowly dies out
t2.html
<html>
<body>
<iframe src="t1.html"></iframe>
</body>
</html>
t1.html
<html>
<body>
<script>location.hostname="blog.com";</script>
</body>
</html>
On 2/15/07, pdp (architect) <pdp.gnucitizen@googlemail.com> wrote:
the first one runs in about:blank which is restricted. the second one
is very interesting but still not very useful because it acts like
about:blank. hmmm it seams that the hostname field has been seriously
overlooked.
On 2/15/07, Michal Zalewski <lcamtuf@dione.ids.pl> wrote:
On Thu, 15 Feb 2007, pdp (architect) wrote:
I wander whether we can execute code on about:config or about:cache.
Actually, there are several odd problems related to location updates and
location.hostname specifically, including one scenario that apparently
makes the script run with document.location in about: namespace.
I did not research them any further, so I can't say if they're
exploitable - but you can see a demo here, feel free to poke around:
http://lcamtuf.coredump.cx/fftests.html
Cheers,
/mz
http://lcamtuf.coredump.cx/
--
pdp (architect) | petko d. petkov
http://www.gnucitizen.org
--
pdp (architect) | petko d. petkov
http://www.gnucitizen.org
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/
