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/

Reply via email to