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

Message-ID: <4E786AF7.1030908@kirils.com>
Date: Tue, 20 Sep 2011 13:29:11 +0300
From: Kirils Solovjovs <kirils.solovjovs@...ils.com>
To: full-disclosure@...ts.grok.org.uk
Subject: Possibility to exploit bash "*" processing

Brought this up a year ago. Seems that no attention has been given to
this so far.

See this screenshot for PoC:
http://02.lv/f/2010/08/05/poc-launums.png

here's a non-destructive PoC:
http://02.lv/f/2010/08/05/poc-*.png

One solution would be to modify "*" processing so that it ignores
filenames that start "-" similarly as it ignores filenames that start
with "."

Or we could just train users to always type "--" before the list of
arguments. :)

-- 
Kirils Solovjovs

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