From: ludo@gnu.org (Ludovic Courtès)
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org
Subject: Re: CVE-2016-0634 code execution in Bash prompt when expanding hostname
Date: Thu, 22 Sep 2016 00:42:15 +0900 [thread overview]
Message-ID: <87d1jxi7jc.fsf@gnu.org> (raw)
In-Reply-To: <20160921052048.GA21274@jocasta.intra> (John Darrington's message of "Wed, 21 Sep 2016 07:20:48 +0200")
John Darrington <john@darrington.wattle.id.au> skribis:
> On Tue, Sep 20, 2016 at 04:55:30PM -0400, Leo Famulari wrote:
> Any advice on how we should handle CVE-2016-0634?
>
> http://seclists.org/oss-sec/2016/q3/534
>
> Like the comment there says, it is only a problem if the machine has
> already been owned,
… or if a privilege application like a DHCP client can be made to set
the host name to $(something bad), which was apparently possible at some
point.
> so I don't see what the issue is. If there is an issue it is for the
> bash maintainers to patch.
Chet proposed a patch:
http://seclists.org/oss-sec/2016/q3/att-538/prompt-string-comsub.patch
IIUC, the just-released 4.4 isn’t affected, right?
We should at least update it in core-updates, but core-updates won’t be
merged until we have fixed that Binutils/MIPS issue (which shouldn’t be
too hard, but we never know!).
I’m somewhat unavailable these days; could someone look into it?
Thanks for the heads-up Leo, as usual!
Ludo’.
next prev parent reply other threads:[~2016-09-21 15:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 20:55 CVE-2016-0634 code execution in Bash prompt when expanding hostname Leo Famulari
2016-09-21 5:20 ` John Darrington
2016-09-21 15:42 ` Ludovic Courtès [this message]
2016-09-27 21:26 ` Leo Famulari
2016-09-30 16:17 ` Bash 4.4 upgrade Ludovic Courtès
2016-09-30 17:27 ` Leo Famulari
2016-09-30 22:04 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d1jxi7jc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=john@darrington.wattle.id.au \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).