Shellshock and how to Patch it

Shellshock and how to Patch it

Shellshock, also known as Bashdoor or the Bash bug, is a security bug, disclosed 24 September 2014 in the widely-used Unix Bash shell. The bug causes Bash to execute commands from environment variables unintentionally. While Bash is not an Internet-facing service, many Internet-facing daemons call it internally, allowing an attacker to use an Internet-facing service that sets the contents of an environmental variable to have Bash execute the commands in the variable. DHCP clients are also potentially vulnerable, and more affected services are expected to be found.

The bug was discovered 12 September 2014 by Stéphane Chazelas, who suggested the name “bashdoor”. The bug was assigned the CVE identifier CVE-2014-6271, kept under embargo until 24 September 2014 14:00 UTC, in order to ensure that security updates were available for most systems[5] as soon as the details were made public. Within days, a series of further related vulnerabilities in Bash were found – CVE-2014-7169, CVE-2014-7186 and CVE-2014-7187 – leading to the need for further patches.

How to check you are vulnerable, open terminal and type the command from the pic:

How to Patch it : sudo apt-get update && sudo apt-get upgrade

Check now its Patched or not, you will see message “Patch it lol” only, so it means bash not allowing to execute command from environmental variables. so you are safe now


Bookmark the permalink.


  1. Is your girlfriend in background ?

  2. How to check Shell Shock Vulnerability in Bash(Linux os & Server)

    Open bash/terminal: env VAR=’ () { :; }; echo Alert Bash is Vulnerable to Shell Shock…!!! ‘ bash -c “echo Bash is not Vulnerable”

    Solution for Shell Shock Vulnerability

    1) ubuntu,Linux mint,Kali Linux

    Sudo apt-get update && sudo apt-get install –only-upgrade bash

    2)Red Hat,Fedora,Centos etc

    Sudo yum update bash

  3. how to fix cd desktop
    bash: cd: desktop: No such file or directory

Leave a Reply

Your email address will not be published. Required fields are marked *