[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANDc0N+RU6oJ0aDYUGGB6o9AQCD9HODEX58+r838Kzf3Ly=mPw@mail.gmail.com>
Date: Tue, 22 Apr 2014 15:46:48 +0800
From: Eduardo Tongson <propolice@...il.com>
To: oss-security@...ts.openwall.com
Subject: Re: CVE Request: Nagios Remote Plugin Executor <= 2.15 Remote Command Execution
On Tue, Apr 22, 2014 at 12:11 PM, <cve-assign@...re.org> wrote:
> ...
> Use CVE-2014-2913.
>
>
Thanks.
> We have not seen additional comments about whether \r would prevent an
> alternate attack approach. If it does, a separate CVE ID would be
> assigned. We do not know of a version of Bash in which \r separates
> commands in the same way that \n does. For example:
>
> % /bin/bash -c "`echo -e "echo a\x0aecho b"`" | cat -v
> a
> b
> % /bin/bash -c "`echo -e "echo a\x0decho b"`" | cat -v
> a^Mecho b
>
Agreed. It's pointless to add a bunch of characters to a blacklist if
they do not have any effect.
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.
