full-disclosure - Re: noise about full-width encoding bypass?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <242a0a8f0705211136x5148926w3d365d7a4f404bd0@mail.gmail.com>
Date: Mon, 21 May 2007 14:36:59 -0400
From: "Brian Eaton" <eaton.lists@...il.com>
To: "Web Security" <websecurity@...appsec.org>, 
	Full-Disclosure <full-disclosure@...ts.grok.org.uk>
Subject: Re: noise about full-width encoding bypass?

On 5/21/07, Brian Eaton <eaton.lists@...il.com> wrote:
> Has anyone had a look at the full-width unicode encoding trick discussed here?
>
> http://www.kb.cert.org/vuls/id/739224
>
> AFAICT, this technique could be useful for a homograph attack.  I
> don't think it's useful for much else.  However, a few vendors have
> reacted already, so I may be missing something important.

To summarize what I've heard from various sources: I am missing
something important. =)  Both PHP and ASP.NET will decode these
characters into their ASCII equivalents.  I don't think J2EE apps are
vulnerable, but this is definitely useful for more more than just
homograph attacks.

Thanks to the various people who have tested this out!

Regards,
Brian

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/