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 201804-13 ] ncurses: Multiple vulnerabilities
Date: Tue, 17 Apr 2018 14:19:39 -0400	[thread overview]
Message-ID: <20180417181939.GA10079@monkey> (raw)

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 201804-13
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: ncurses: Multiple vulnerabilities
     Date: April 17, 2018
     Bugs: #624644, #625830, #629276, #639706
       ID: 201804-13

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

Synopsis
========

Multiple vulnerabilities have been found in ncurses, the worst of which
allows remote attackers to execute arbitrary code.

Background
==========

Free software emulation of curses in System V.

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

    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  sys-libs/ncurses             < 6.1:0                    >= 6.1:0

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

Multiple vulnerabilities have been discovered in ncurses. Please review
the CVE identifiers referenced below for details.

Impact
======

A remote attacker, by enticing the user to process untrusted terminfo
or other data, could execute arbitrary code or cause a Denial of
Service condition.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All ncurses users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=sys-libs/ncurses-6.1:0"

References
==========

[  1 ] CVE-2017-10684
       https://nvd.nist.gov/vuln/detail/CVE-2017-10684
[  2 ] CVE-2017-10685
       https://nvd.nist.gov/vuln/detail/CVE-2017-10685
[  3 ] CVE-2017-11112
       https://nvd.nist.gov/vuln/detail/CVE-2017-11112
[  4 ] CVE-2017-11113
       https://nvd.nist.gov/vuln/detail/CVE-2017-11113
[  5 ] CVE-2017-13728
       https://nvd.nist.gov/vuln/detail/CVE-2017-13728
[  6 ] CVE-2017-13729
       https://nvd.nist.gov/vuln/detail/CVE-2017-13729
[  7 ] CVE-2017-13730
       https://nvd.nist.gov/vuln/detail/CVE-2017-13730
[  8 ] CVE-2017-13731
       https://nvd.nist.gov/vuln/detail/CVE-2017-13731
[  9 ] CVE-2017-13732
       https://nvd.nist.gov/vuln/detail/CVE-2017-13732
[ 10 ] CVE-2017-13733
       https://nvd.nist.gov/vuln/detail/CVE-2017-13733
[ 11 ] CVE-2017-13734
       https://nvd.nist.gov/vuln/detail/CVE-2017-13734
[ 12 ] CVE-2017-16879
       https://nvd.nist.gov/vuln/detail/CVE-2017-16879

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

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

 https://security.gentoo.org/glsa/201804-13

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 2018 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: Digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2018-04-17 18:25 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=20180417181939.GA10079@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