Topic: Shellshock bug how to avoid (Read 962 times)

National Cyber Awareness System:
TA14-268A: GNU Bourne Again Shell (Bash) ‘Shellshock’ Vulnerability (CVE-2014-6271,CVE-2014-7169)
09/25/2014 12:56 PM EDT

Original release date: September 25, 2014
Systems Affected
•   GNU Bash through 4.3.
•   Linux, BSD, and UNIX distributions including but not limited to:
o   CentOS 5 through 7
o   Debian
o   Mac OS X
o   Red Hat Enterprise Linux 4 through 7
o   Ubuntu 10.04 LTS, 12.04 LTS, and 14.04 LTS
Overview
A critical vulnerability has been reported in the GNU Bourne Again Shell (Bash), the common command-line shell used in most Linux/UNIX operating systems and Apple’s Mac OS X. The flaw could allow an attacker to remotely execute shell commands by attaching malicious code in environment variables used by the operating system [1]. The United States Department of Homeland Security (DHS) is releasing this Technical Alert to provide further information about the GNU Bash vulnerability.
Description
GNU Bash versions 1.14 through 4.3 contain a flaw that processes commands placed after function definitions in the added environment variable, allowing remote attackers to execute arbitrary code via a crafted environment which enables network-based exploitation. [2, 3]
Critical instances where the vulnerability may be exposed include: [4, 5]
•   Apache HTTP Server using mod_cgi or mod_cgid scripts either written in bash, or spawn subshells.
•   Override or Bypass ForceCommand feature in OpenSSH sshd and limited protection for some Git and Subversion deployments used to restrict shells and allows arbitrary command execution capabilities.
•   Allow arbitrary commands to run on a DHCP client machine, various Daemons and SUID/privileged programs.
•   Exploit servers and other Unix and Linux devices via Web requests, secure shell, telnet sessions, or other programs that use Bash to execute scripts.
Impact
This vulnerability is classified by industry standards as “High” impact with CVSS Impact Subscore 10 and “Low” on complexity, which means it takes little skill to perform. This flaw allows attackers to provide specially crafted environment variables containing arbitrary commands that can be executed on vulnerable systems. It is especially dangerous because of the prevalent use of the Bash shell and its ability to be called by an application in numerous ways.
Solution
Patches have been released to fix this vulnerability by major Linux vendors for affected versions. Solutions for CVE-2014-6271 do not completely resolve the vulnerability. It is advised to install existing patches and pay attention for updated patches to address CVE-2014-7169.
Many UNIX-like operating systems, including Linux distributions, BSD variants, and Apple Mac OS X include Bash and are likely to be affected. Contact your vendor for updated information. A list of vendors can be found in CERT Vulnerability Note VU#252743 [6].
US-CERT recommends system administrators review the vendor patches and the NIST Vulnerability Summary for CVE-2014-7169, to mitigate damage caused by the exploit.
References
•   Ars Technica, Bug in Bash shell creates big security hole on anything with *nix in it;
•   DHS NCSD; Vulnerability Summary for CVE-2014-6271
•   DHS NCSD; Vulnerability Summary for CVE-2014-7169
•   Red Hat, CVE-2014-6271
•   Red Hat, Bash specially-crafted environment variables code injection attack
•   CERT Vulnerability Note VU#252743
Revision History
•   September 25, 2014 - Initial Release

Wait till the hackers find this post....

ok cool. Thanks

Yes.

well that didnt answwer my question really

It is safe to say, if you don't use mac you are relatively safe and save a lot of money

Is it safe to say that if you leave your mac computer switched off untill an update is ready you will be relatively safe?