"Shellshock" bash bug

[Graham Watkins]

On 26/09/14 16:43, Kevin O'Gorman wrote:
> There has been a code-injection vulnerability in bash for the last 22
> years, recently discovered and named "Shellshock".  It's nasty.
> http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-6271
>
> Here's a quick one-liner to see if you're vulnerable:
> $ env x='() { :;}; echo vulnerable'  bash -c "echo this is a test"
> vulnerable
> this is a test
> $
>
> If you get that result, update your bash from the repositories, and all
> should be well:
> $ env x='() { :;}; echo vulnerable'  bash -c "echo this is a test"
> bash: warning: x: ignoring function definition attempt
> bash: error importing function definition for `x'
> this is a test
> $
>
> Safe computing to all
>
>
> --
> Kevin O'Gorman
> #define QUESTION ((bb) || (!b))  /* Shakespeare */
>
> 	Please consider the environment before printing this email.
>
>
>
>
The result I get is:

"$: command not found"

Is that good?

Cheers,

Graham