From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] bash exploit heads up
Date: Wed, 24 Sep 2014 14:45:22 -0700 [thread overview]
Message-ID: <CAA93jw6ssG9624d+HrZuVwdE00r5=qNSv0va3dQweUJLbqjthw@mail.gmail.com> (raw)
From fiddling with busybox's ash shell... thus far it *does NOT*
appear vulnerable to this.
http://linux.slashdot.org/story/14/09/24/1638207/remote-exploit-vulnerability-found-in-bash
Simple test:
env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
shows vulnerable for bash, not sh, on openwrt and cerowrt. That said,
it makes me nervous. I've never really liked the redir.sh method cero
uses to bounce people to the right web interface... suggestions to do
it in javascript or something safer desired.
and I'm aware that several people do run bash on cero, so be aware of
this issue.
--
Dave Täht
https://www.bufferbloat.net/projects/make-wifi-fast
next reply other threads:[~2014-09-24 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 21:45 Dave Taht [this message]
2014-09-24 21:51 ` Toke Høiland-Jørgensen
2014-09-24 21:54 ` Eric S. Johansson
2014-09-24 22:00 ` Eric S. Johansson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6ssG9624d+HrZuVwdE00r5=qNSv0va3dQweUJLbqjthw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox