[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5422EC08.7000905@case.edu>
Date: Wed, 24 Sep 2014 12:06:32 -0400
From: Chet Ramey <chet.ramey@...e.edu>
To: "Alexander E. Patrakov" <patrakov@...il.com>,
oss-security@...ts.openwall.com
CC: chet.ramey@...e.edu
Subject: Re: CVE-2014-6271: remote code execution through bash
On 9/24/14, 12:01 PM, Alexander E. Patrakov wrote:
>> I see no good workaround. Starting the forced command with "unset
>> SSH_ORIGINAL_COMMAND &&" does not help - we'd need to unset the variable
>> before starting bash, not from bash.
>
> Won't installing dash and setting the shell of users who have forced
> commands to dash mitigate this somehow?
Why not install the publicly-available bash patches and rebuild bash?
That's the real solution.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU chet@...e.edu http://cnswww.cns.cwru.edu/~chet/
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
