Shellshock bug exposes web servers, home routers

Third Certainty | September 26, 2014

“Step one is to figure out if you have any systems that are vulnerable. If so, how many? Step two is to figure out how to put a compensating control in place to buy time to wait for a patch. Step three, patch your systems in a methodical manner to ensure your most important servers are fixed first.” advises Jeff Schilling, CSO of secure cloud provider Firehost.