Size: 3225
Comment: Apparently there's a final fix out now
|
Size: 3333
Comment: Add another link
|
Deletions are marked like this. | Additions are marked like this. |
Line 29: | Line 29: |
* [[https://shellshocker.net/|"shellshocker.net", and online tool for testing if a system is vulnerable]] |
What is the Shellshock vulnerability in Bash?
As of this writing (September 27th, 2014), the situation with Shellshock is changing so rapidly that you're probably better off using your preferred search engine instead of this FAQ. For example, you could search a news site for recent items which contain the word "Shellshock".
A quick summary is this:
- The most recent updates should now fix all known Shellshock-related vulnerabilities.
- Many systems were never vulnerable to a remote attack, but it's safer to patch all systems anyway.
- Other potential problems were identified during the investigation, but are considered separate from the Shellshock bug.
After things stabilize a bit, this FAQ page should be updated with a better summary. For information about specific vulnerabilities related to Shellshock, you may find better results by searching for terms such as "CVE-2014-6271", "CVE-2014-7169", "CVE-2014-7186", or "CVE-2014-7187".
In the meantime, here are a few links that should help you get started:
ZDNet: the latest patches do fix all known Shellshock issues
Search Google News for 'Shellshock bash', limited to the last 24 hours
"shellshocker.net", and online tool for testing if a system is vulnerable
Summary article from RedHat on how to determine if a system is vulnerable
Official US-CERT page on CVE-2014-6271, the first vulnerability in the series to be discovered
"Everything you need to know about the Shellshock Bash bug", by Troy Hunt