I am not sure the intended point of the exploit since you have @roguehost and not a proper POC, but I believe all you have triggered is normal behavior for auto logging into .htaccess protected folders in the form username:[EMAIL PROTECTED]
http://forum.sambarserver.info/viewtopic.php?p=288 http://www.freewebmasterhelp.com/tutorials/htaccess/3 I did it with google.com and @mail.yahoo.com and it tried to log me into mail.yahoo.com with google.... as my username as expected On Feb 4, 2008 2:10 PM, carl hardwick <[EMAIL PROTECTED]> wrote: > Firefox seems to have trouble with defining the proper hostname when > requesting a ssl connection. I was able to trick Firefox in thinking > the hostname behind the at-sign is legit and the same as the URI that > requested an ssl connection, and this without a warning. > > PoC: https://[EMAIL PROTECTED] > > You can add as much garbage between .com and the @ sign. > > So what else can we do? > > PoC: > [EMAIL PROTECTED] > [EMAIL PROTECTED] > > ah heck we don't need that at all: > [EMAIL PROTECTED] > > works fine also :) > > _______________________________________________ > Full-Disclosure - We believe in it. > Charter: http://lists.grok.org.uk/full-disclosure-charter.html > Hosted and sponsored by Secunia - http://secunia.com/ >
_______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
