With comments like this (and about 75% of the other juvenile comments) it's really hard to come to these forum and expect to get useful information without wading through enormous piles of cr*p presumably posted by pimply adolescents who can't get dates and spend their time thinking of ways to post useless, but completely unfunny, comments.
bash -c "true $(printf '<<EOF %.0s' {1..79})" 2> /dev/null
Do I need to install MacOS X 10.9.5 update first ???
I came across this to check for vulnerabilities: https://github.com/hannob/bashcheck . It reports that the updates from Apple, 3.2.54, and 4.3.27 are still vulnerable to CVE-2014-7186 (redir_stack bug).
sucks for yosemite users.
Did I miss something, 10.9.5 or later, what for the love of apples is later than 10.9.5??
Did I miss something, 10.9.5 or later, what for the love of apples is later than 10.9.5??
I don't see this in regular software update, isn't this important enough to show there?![]()
This test indicates that bash is "vulnerable" because bash gives a segmentation fault there. Because Apple's patch won't pass functions by default, the concern isn't that bash is truly vulnerable, but rather that the crash could potentially open up some other access, same as the crash of any other binary.
More in-depth testing on CVE-2014-7186 is here: https://lists.gnu.org/archive/html/bug-bash/2014-09/msg00238.html
Aside from that fault, Apple's bash after this patch is not vulnerable.
Isn't that the point of CVE-2014-7186 though, that the segfault is an opening, even if it's a pain to exploit? I feel better that the low hanging fruit issues were patched, but still uneasy that bash can be crashed so easily. I'll keep following that mail thread to see if I should be more concerned.
I don't really care for myself, but not being in Software Update/App Store Updates means inexpert users won't know about or get it, nor will it flow down to enterprise management systems which replicate from Apple's main system (aka local Software Update server, e.g.: as found in OS X Server).