Full Disclosure mailing list archives
Re: Possibility to exploit bash "*" processing
From: Valdis.Kletnieks () vt edu
Date: Wed, 21 Sep 2011 15:12:21 -0400
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).
Attachment:
_bin
Description:
_______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
Current thread:
- Possibility to exploit bash "*" processing Kirils Solovjovs (Sep 20)
- Re: Possibility to exploit bash "*" processing Valdis . Kletnieks (Sep 20)
- Re: Possibility to exploit bash "*" processing GloW - XD (Sep 20)
- Re: Possibility to exploit bash "*" processing Cédric Jeanneret (Sep 21)
- Re: Possibility to exploit bash "*" processing Jacqui Caren (Sep 21)
- Re: Possibility to exploit bash "*" processing Dan Carpenter (Sep 21)
- Re: Possibility to exploit bash "*" processing Valdis . Kletnieks (Sep 21)
- Re: Possibility to exploit bash "*" processing Andrew Farmer (Sep 21)
- Re: Possibility to exploit bash "*" processing Valdis . Kletnieks (Sep 21)
- Re: Possibility to exploit bash "*" processing Valdis . Kletnieks (Sep 21)
- Re: Possibility to exploit bash "*" processing Valdis . Kletnieks (Sep 20)