full-disclosure - Re: Possibility to exploit bash "*" processing

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] [day] [month] [year] [list]

Message-ID: <13213.1316632341@turing-police.cc.vt.edu>
Date: Wed, 21 Sep 2011 15:12:21 -0400
From: Valdis.Kletnieks@...edu
To: Andrew Farmer <andfarm@...il.com>
Cc: full-disclosure@...ts.grok.org.uk, Dan Carpenter <error27@...il.com>
Subject: Re: Possibility to exploit bash "*" processing

On Wed, 21 Sep 2011 11:36:32 PDT, Andrew Farmer said:

> Not true - the multibyte sequences in UTF-8 text consist entirely of
> high-bit characters (0xC2 - 0xF4 initial, 0x80 - 0xBF continuation). All
> characters below 0x80, including ASCII control characters, are always
> mapped directly to the corresponding codepoints.

Well, if you want to be pedantic about it. ;)

OK, they're "nonprintable characters" - which *still* should be filtered out if
you're filtering out control characters (if you're tossing a hex 0x17 because
it may give software indigestion, you probably should be tossing a 0x97 as
well).

Content of type "application/pgp-signature" skipped

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