News for hackers. Stuff that matters.
Re:Everything you need to know about the Shellshock Bash bug by danso on Thursday September 25, 2014 @09:26AM (#8366962)
In another thread, I saw that this was an easy check to see if your bash was affected:

     env X="() { :;} ; echo busted" /bin/sh -c "echo stuff"
If you get "busted" back, then you're affected...which is what I get with Mac OS X 10.9...however, when I try it on an Ubuntu server (14.x) that hasn't been patched in awhile...I don't get the error...Er, why is that? I thought this pretty much affected every bash since 25 years ago?

(Someone else in this thread mentioned that Ubuntu uses dash...so...all modern Ubuntu servers are OK?)

Re:Everything you need to know about the Shellshock Bash bug by lambda on Thursday September 25, 2014 @10:11AM (#8367221)
No, you are not OK. Replace "sh" in that command with "bash" and you should still see the issue.

There is a lower likelihood that you'll see the issue, as anything which just uses sh (including the "system" function, and similar ones) will use dash indeed of Bash; but there will still be places where bash is called explicitly, including many shell scripts that depend on bash features, which are vulnerable.

Re:Everything you need to know about the Shellshock Bash bug by spacehunt on Thursday September 25, 2014 @09:27AM (#8366967)
Debian-based systems use dash instead of bash for /bin/sh. But if you have scripts that explicitly use bash, you are still at risk.
Re:Everything you need to know about the Shellshock Bash bug by djengineerllc on Thursday September 25, 2014 @10:09AM (#8367205)
I tried this and it didn't work on my Ubuntu machine, it echoed "stuff". env X="() { :;} ; echo busted" /bin/sh -c "echo stuff"

But then I tried this command and it echoed "vulnerable". env var='() { ignore this;}; echo vulnerable' bash -c /bin/true

Re:Everything you need to know about the Shellshock Bash bug by muyuu on Thursday September 25, 2014 @10:26AM (#8367314)
AFAIK bash is the default terminal shell in all Ubuntus. So yeah, you're affected.
Re:Everything you need to know about the Shellshock Bash bug by bodyfour on Thursday September 25, 2014 @11:50AM (#8367754)
The attack isn't against terminal shells. The biggest risk is against things that use the shell implicitly like system()/popen()/etc and they all use /bin/sh

It's certainly possible to be at risk if, for instance, you had a CGI script that was specifically written in bash (i.e. starts with "#!/bin/bash") but that's a lot less likely.

So definitely patch your Debian/Ubuntu/etc machines but do your Redhat-based ones (and other places where "/bin/sh --version" indicates that it's bash) first.

Re:Everything you need to know about the Shellshock Bash bug by gknoy on Thursday September 25, 2014 @12:10PM (#8367893)
It seems arbitrarily risky to say, effectively, "My bash is vulnerable, but it's OK because it's unlikely to be called due to the defaults being Something Else" -- that might be short-term reassurance, but it sure sounds safer to fix it even if you don't think it can be exploited.
Re:Everything you need to know about the Shellshock Bash bug by muyuu on Thursday September 25, 2014 @02:06PM (#8368605)
By default I mean that new users are given bash as sh by default, including the users for daemon services. So unless you assigned a different shell, or the service specifically asked for a shell other than the default linked by /bin/sh, then they will be running bash.