Updating from bash
It’s likely you’ve already done this step before coming here, but here’s how to check to see if you’re vulnerable to the Shellshock Bug.
Check your vulnerability by running the following tests from your shell: Running the following command in a shell.
Don’t attempt accidentally remove your /bin/echo file, you can restore it by searching for an archive of the core-utils RPM package for your particular system, then use “rpm -iv –replacepkgs” when installing it to force it to re-install and restore the deleted /bin/echo file. If you see “CVE-2014-7187 vulnerable, word_lineno” as part of the output, you are vulnerable to this exploit.
If the above command outputs the current date (it may also show errors), you are still vulnerable.If it just spits out the word “date,” then you’re fine against this exploit.This entry was posted in Linux Reference Technology and tagged bash bug Fedora 14 Fedora 15 Fedora 16 Fedora 17 Fedora 18 Fedora 19 GNU patch patch bash manually patch old Fedora shellshock shellshock bug on With the announcement of the Shellshock Bash Bug, Linux admins around the world have been scrambling to patch their Bash shells so that they’re no longer vulnerable to the exploit.If you have a Fedora, RHEL, or Cent OS system that hasn’t reached End-Of-Life, then updating to a patched version of Bash is as simple as: But what if you have a system running Fedora 12, Fedora 13, Fedora 14, Fedora 15, Fedora 16, Fedora 17, Fedora 18, or Fedora 19…or even RHEL/Cent OS 3 or RHEL/Cent OS 4, or an older SUSE Linux box?
I have a Fedora 12 box I keep around for testing, and an updated version of Bash isn’t available in the repos.