News for hackers. Stuff that matters.
Re:Everything you need to know about the Shellshock Bash bug by IshKebab on Thursday September 25, 2014 @01:17PM (#8368281)
I have no sympathy really for people who use `system()`-style calls, or bash in their web servers. Bash is fairly obviously designed with complete disregard for security. I seriously doubt this is its last major flaw.

But anyway, is it really that common? I would have thought most CGI scripts are Python, Perl, PHP, etc. and don't use `system()` type calls. Right?

Re:Everything you need to know about the Shellshock Bash bug by rlucas on Thursday September 25, 2014 @01:41PM (#8368419)
No, super wrong. Underneath the hood there are all kinds of things that go on and result in system() or similar calls. Think about every module in CPAN / PyPI / whatever. Any non-trivial Web app has a high likelihood of eventually, somehow, somewhere, causing a system() type call to fire off.
Re:Everything you need to know about the Shellshock Bash bug by shangxiao on Thursday September 25, 2014 @01:32PM (#8368365)
This is actually quite common and acceptable if you want to interact with a piece of software for which there is no library or api. One real world example is producing thumbnails from Word documents using Libre Office.
Re:Everything you need to know about the Shellshock Bash bug by argggh on Thursday September 25, 2014 @02:14PM (#8368649)
You don't have to do it explicitly either. In Perl, for instance, doing stuff like open($tgz, "|-", "gzip | tar -cvf /tmp/file.tgz"); is going to cause execution of /bin/sh behind the scenes. Assuming that /bin/sh is never called during processing of external requests is risky.