News for hackers. Stuff that matters.
Re:CVE-2014-6271: Remote code execution through bash by pbhjpbhj on Wednesday September 24, 2014 @09:03PM (#8364999)
Surely though the CGI framework sanitises the headers first? Otherwise this seems like it's a pretty predictable problem - isn't "always sanitise user data" the cardinal rule of backends.

I can certainly imagine that I might have designed a web page that passed user input direct to a BASH script to do a ping or some such, but not if it's public facing.

Re:CVE-2014-6271: Remote code execution through bash by AgentME on Wednesday September 24, 2014 @10:03PM (#8365179)
What sanitization do you expect the CGI framework to apply to the header value representing the user agent? str_replace($userAgent, '() {', 'no bash bug for you')?

Only a few environment variables are given any meaning by the system. Other environment variables don't have any predefined meaning and can be any null-terminated string.

Re:CVE-2014-6271: Remote code execution through bash by pbhjpbhj on Thursday September 25, 2014 @08:20PM (#8370597)
Indeed, lol. It's a bit clearer to me now. Thanks for your comment.

It seems like a sort of loose typing issue. Perhaps if when setting environment variables the app using them could specify a type (eg nonExecutableText) such that bash knows it's receiving textual content that mustn't be executed; would that help?

Re:CVE-2014-6271: Remote code execution through bash by SwellJoe on Wednesday September 24, 2014 @09:20PM (#8365041)
One of the comments in this thread (http://seclists.org/oss-sec/2014/q3/650 ), seems to indicate that Apache is an attack vector for this vulnerability.