public inbox for gentoo-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Aaron Bauman <bman@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 201903-02 ] Zsh: User-assisted execution of arbitrary code
Date: Sat, 9 Mar 2019 21:22:31 -0500	[thread overview]
Message-ID: <20190310022231.GB3008@monkey> (raw)

[-- Attachment #1: Type: text/plain, Size: 2787 bytes --]

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 201903-02
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: Zsh: User-assisted execution of arbitrary code
     Date: March 10, 2019
     Bugs: #665278
       ID: 201903-02

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis
========

Input validation errors in Zsh could result in arbitrary code
execution.

Background
==========

A shell designed for interactive use, although it is also a powerful
scripting language.

Affected packages
=================

    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  app-shells/zsh                < 5.6                       >= 5.6 

Description
===========

Two input validation errors have been discovered in how Zsh parses
scripts:

* Parsing a malformed shebang line could cause Zsh to call a program
  listed in the second line (CVE-2018-0502)
* Shebang lines longer than 64 characters are truncated
  (CVE-2018-13259)

Impact
======

An attacker could entice a user to execute a specially crafted script
using Zsh, possibly resulting in execution of arbitrary code with the
privileges of the process.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All Zsh users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=app-shells/zsh-5.6"

References
==========

[ 1 ] CVE-2018-0502
      https://nvd.nist.gov/vuln/detail/CVE-2018-0502
[ 2 ] CVE-2018-13259
      https://nvd.nist.gov/vuln/detail/CVE-2018-13259

Availability
============

This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

 https://security.gentoo.org/glsa/201903-02

Concerns?
=========

Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users' machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.

License
=======

Copyright 2019 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2019-03-10  2:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20190310022231.GB3008@monkey \
    --to=bman@gentoo.org \
    --cc=gentoo-announce@lists.gentoo.org \
    --cc=security@gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox