From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: shawn wilson <ag4ve.us@gmail.com>,
Zsh Hackers' List <zsh-workers@zsh.org>
Subject: Re: zsh 5.0.7 released
Date: Thu, 9 Oct 2014 21:48:06 +0100 [thread overview]
Message-ID: <20141009214806.201e9c0d@pws-pc.ntlworld.com> (raw)
In-Reply-To: <CAH_OBieFY24--_Ka637pM0g-iKEKLrnz4zXLcWKj9_mx+DKn=w@mail.gmail.com>
Oct 2014 09:55:50 -0400
shawn wilson <ag4ve.us@gmail.com> wrote:
> On Oct 8, 2014 9:56 PM, "Peter Stephenson" <p.w.stephenson@ntlworld.com>
> wrote:
> >
> > Version 5.0.7 of zsh is released. You can get it from
> > http://www.zsh.org/pub and mirrors (see below). This is a stable
> > release. There are minor new features as well as bug fixes since 5.0.6.
> >
> > Note in particular there is a security fix to disallow evaluation of the
> > initial values of integer variables imported from the environment (they
> > are instead treated as literal numbers). That could allow local
> > privilege escalation, under some specific and atypical conditions where
> > zsh is being invoked in privilege elevation contexts when the
> > environment has not been properly sanitized, such as when zsh is invoked
> > by sudo on systems where "env_reset" has been disabled.
> >
>
> Was this security issue in SSH discussed on the list somewhere (I can't
> seem to find other mention of it outside the readme - not even direct
> mention in changelog or git log)...?
I don't know of an ssh issue, but the sudo issue was discussed offline.
The original point about sanitising integer imports, however, was discussed
here.
pws
next parent reply other threads:[~2014-10-09 20:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20141008193835.5d66c0ad@pws-pc.ntlworld.com>
[not found] ` <CAH_OBieFY24--_Ka637pM0g-iKEKLrnz4zXLcWKj9_mx+DKn=w@mail.gmail.com>
2014-10-09 20:48 ` Peter Stephenson [this message]
2014-10-09 22:41 ` shawn wilson
2014-10-10 1:54 ` Bart Schaefer
2014-10-11 22:53 ` shawn wilson
2014-10-11 0:18 ` Simon Ruderich
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=20141009214806.201e9c0d@pws-pc.ntlworld.com \
--to=p.w.stephenson@ntlworld.com \
--cc=ag4ve.us@gmail.com \
--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).