Are you susceptible to the latest ‘evil’ ShellShock bug? If you have a mac or linux, try this.

UPDATE: For you mac users, here is the current patch: http://support.apple.com/kb/HT6495

You HOPEFULLY have heard about this new issue, or ‘bug‘ that many computers probably have.

If you haven’t, its called the Shellshock bash bug – its bad, real bad.

So first, do you have a windows machine? If yes, you are PROBABLY just fine – except if you have a server somewhere, then it probably is vulnerable to the bug…

So is your data on servers that are vulnerable, what servers are vulnerable? A lot of them.

So sleep easy knowing that your data may become someone else’s… sorry I’m just fear mongering.

Here’s the test:

If you have a mac, press ‘Command’ + ‘Space’, the start typing ‘terminal’ one you see terminal, click on it. Or in linux open your terminal.

You should see something like this:
Screen Shot 2014-09-26 at 8.33.47 AM

env X="() { :;} ; echo busted" /bin/sh -c "echo stuff"

When you enter the above, it should look like this (if vulnerable effected):

Screen Shot 2014-09-26 at 8.34.22 AM

If you have a linux computer, here is a link to the fix: https://access.redhat.com/articles/1200223

Though it should be noted, you won’t be totally safe.

What if I have a mac?

Well, we’re actually temporarily out of luck. Having the latest macbook pro model with all of the updates still doesn’t preclude you from vulnerability – after all thats what I have. Apple has claimed that it doesn’t effect many users, though being totally up to date and being vulnerable, I think that’s BS.

We have to wait for apple to come with an update for Mac before we can do anything. By the time you read this there may be one, check by clicking on the apple symbol in the top left, and click ‘software update’. Hopefully something will be there that fixes this bug, but for now.

Solution?

Close your computer for a few days, or day, or some amount of time. Turn it off, read a book, turn off internet, it’ll probably be a better day for you anyways. Sit back and enjoy your non-tech comforts.

A great tech article on this bug can be found here. The bash script I got from Troy Hunt in that post.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s