[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Help-bash] Patching shellshock fixes for 2.05

From: Mohan Kannekanti
Subject: Re: [Help-bash] Patching shellshock fixes for 2.05
Date: Thu, 2 Oct 2014 13:03:51 -0700

​Hi Chet,

Thanks for the reply.

I am sorry, I am bit confused. Do you mean that 2.05 version is not
vulnerable at all ​or those patches should resolve that vulnerability.

I get this after running 'curl | sh' (from on patched bash.

# cat /tmp/ | bash
CVE-2014-6271 (original shellshock): not vulnerable
bash: shellshocker: command not found
CVE-2014-6278 (Florian's patch): not vulnerable
CVE-2014-7169 (taviso bug): not vulnerable
CVE-2014-//// (exploit 3 on not vulnerable
CVE-2014-7186 (redir_stack bug): not vulnerable
bash: line 1: syntax error near unexpected token `;'
bash: line 1: `for x{1..200} in ; do :'
*CVE-2014-7187 (nested loops off by one): VULNERABLE*

Also, I had to manually patch Florian's fix (  as there were
changes in 'mk_env_string()' declaration and also environment variables
storage (Hash tables were introduced).
I am little concerned about the patch too whether it is done correctly or

Can you please help me finding the proper fix.??


On Thu, Oct 2, 2014 at 11:23 AM, Chet Ramey <address@hidden> wrote:

> On 10/2/14, 1:28 PM, Mohan Kannekanti wrote:
> > Hi Team,
> >
> > I am trying to patch the latest fixes for 2.05 using what were given for
> > 2.05b. It looks like bash took lot of changes from 2.05 to 2.05b
> especially
> > how the environment variables are treated.
> >
> > I did manually patched your fixes on 2.05 version. But it looks like
> > CVE-2014-7187 is still vulnerable.
> I doubt it's vulnerable, since the array with the off-by-one access error
> the exploit uses doesn't exist.
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>                  ``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, ITS, CWRU    address@hidden


This electronic message, including attachments, is intended only for the 
use of the individual or company named above or to which it is addressed. 
The information contained in this message shall be considered confidential 
and proprietary, and may include confidential work product. If you are not 
the intended recipient, please be aware that any unauthorized use, 
dissemination, distribution or copying of this message is strictly 
prohibited. If you have received this email in error, please notify the 
sender by replying to this message and deleting this email immediately.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]