News for hackers. Stuff that matters.
Re:CVE-2014-6271: Remote code execution through bash by super_mario on Wednesday September 24, 2014 @02:59PM (#8363419)
Interestingly enough ancient BASH version 3.2 on Mac OS X 10.9.5 is not vulnerable:

    $ echo $BASH_VERSION
    3.2.51(1)-release
    $ x='() { :;}; echo vulnerable' bash -c "echo this is a test"
    bash: warning: x: ignoring function definition attempt
    bash: error importing function definition for `x'
    this is a test
    $
I manually patched my BASH 4.3 to patch level 25 so it's not vulnerable either.

    $ echo $BASH_VERSION
    4.3.25(1)-release
    $ x='() { :;}; echo vulnerable' bash -c "echo this is a test"
    bash: warning: x: ignoring function definition attempt
    bash: error importing function definition for `x'
    this is a test
    $
Re:CVE-2014-6271: Remote code execution through bash by Crito on Wednesday September 24, 2014 @03:17PM (#8363530)
Since other people are reporting that their copies of bash 3.2.51 are vulnerable, I suspect that the version of bash that is currently running in that terminal is 3.2.51 and vulnerable, but the version of bash that you are invoking from that vulnerable version of bash is not.

In other words, I suspect that:

    $ echo $BASH_VERSION
and

    $ bash --version
Will report different version numbers.

If you start a new terminal and try `echo $BASH_VERSION`, you will probably see a different version as well.

Re:CVE-2014-6271: Remote code execution through bash by ak217 on Wednesday September 24, 2014 @03:26PM (#8363572)
Yes - the shell currently running is probably the user's login shell, and the shell in e.g. /usr/local/bin/bash was probably installed by Homebrew or MacPorts.
Re:CVE-2014-6271: Remote code execution through bash by super_mario on Wednesday September 24, 2014 @05:50PM (#8364359)
That could be the reason. I have renamed /bin/bash version 3.2 to /bin/bash3 and copied /usr/local/bin/bash that I build myself to /bin/bash making effectively bash version 4.3 the default login and system shell.

I started bash 3.2 from bash 4.3 so that could be the reason why it is not vulnerable as child process.

Re:CVE-2014-6271: Remote code execution through bash by daveloyall on Wednesday September 24, 2014 @03:26PM (#8363571)
Excellent insight!
Re:CVE-2014-6271: Remote code execution through bash by daveloyall on Wednesday September 24, 2014 @03:06PM (#8363457)
That's ... weird, since the phrase "ignoring function definition attempt" wasn't added to bash 3.2 until today, with patch level 52.

http://ftp.gnu.org/pub/gnu/bash/bash-3.2-patches/bash32-052

Your paste indicates patch level 51.

The phrase in question doesn't appear on the internet much at all before today.

https://www.google.com/search?q="ignoring+function+definitio...

I presume that the one search result we see is due to a server that has an incorrect clock (or a time machine).

Re:CVE-2014-6271: Remote code execution through bash by Fishkins on Wednesday September 24, 2014 @03:06PM (#8363462)
Hmm, I do see "vulnerable" print when I run that code on Mac OS X 10.9.5 with bash 3.2.51(1)-release.
Re:CVE-2014-6271: Remote code execution through bash by aabdocker on Thursday September 25, 2014 @03:43AM (#8366083)
I have same bash version and yet mine is vulnerable on OS X 10.10.