From: "İsmail Dönmez" <ismail@donmez.ws>
To: Frank Terbeck <ft@bewatermyfriend.org>
Cc: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: zsh seems to be vulnerable to CVE-2014-6271: remote code execution through bash
Date: Wed, 24 Sep 2014 17:55:05 +0300 [thread overview]
Message-ID: <CAJ1KOAiJT7eeQXcV1VbU=9A2GqUStm5TLYxEwCzPvowRVJcYog@mail.gmail.com> (raw)
In-Reply-To: <87fvfhvzl9.fsf@ft.bewatermyfriend.org>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
On Wed, Sep 24, 2014 at 5:54 PM, Frank Terbeck <ft@bewatermyfriend.org>
wrote:
> İsmail Dönmez wrote:
> > According to the vulnerability test in
> >
> https://securityblog.redhat.com/2014/09/24/bash-specially-crafted-environment-variables-code-injection-attack/
> >
> > [~]> echo $ZSH_VERSION
> > 5.0.6
> >
> > [~]> env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
> > vulnerable
> > this is a test
> >
> > Looks like zsh is vulnerable too.
>
> Does it?
>
> [snip]
> zsh% x='() { :; }; echo vuln' bash -c 'echo test'
> vuln
> test
> zsh% x='() { :; }; echo vuln' zsh -c 'echo test'
> test
> [snap]
>
> Doesn't look like it to me.
>
> Bash has this weird feature, where you can "export functions". I suspect
> that's what's happening here. Zsh doesn't have this feature. Thankfully
>
Brown paper bag for me not replacing bash with zsh ;) Thanks and sorry for
the noise :)
next prev parent reply other threads:[~2014-09-24 14:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 14:45 İsmail Dönmez
2014-09-24 14:54 ` Frank Terbeck
2014-09-24 14:55 ` İsmail Dönmez [this message]
2014-09-24 15:01 ` Peter Stephenson
2014-09-24 15:08 ` Frank Terbeck
2014-09-24 15:13 ` Jérémie Roquet
2014-09-24 14:55 ` Jérémie Roquet
2014-09-24 14:59 ` Chet Ramey
2014-09-25 13:11 ` Peter Stephenson
2014-09-26 14:03 ` Oliver Kiddle
2014-09-26 20:08 ` Peter Stephenson
2014-09-29 10:04 ` PATCH: safe numeric import Peter Stephenson
2014-09-29 15:24 ` Bart Schaefer
2014-10-01 14:57 ` [Bulk] " Oliver Kiddle
2014-10-02 16:06 ` Peter Stephenson
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ1KOAiJT7eeQXcV1VbU=9A2GqUStm5TLYxEwCzPvowRVJcYog@mail.gmail.com' \
--to=ismail@donmez.ws \
--cc=ft@bewatermyfriend.org \
--cc=zsh-workers@zsh.org \
/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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).