Gentoo: GLSA-201804-13: ncurses: Multiple vulnerabilities
Summary
Multiple vulnerabilities have been discovered in ncurses. Please review the CVE identifiers referenced below for details.
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.
Background
Free software emulation of curses in System V.
Affected Packages
------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 sys-libs/ncurses < 6.1:0 >= 6.1:0
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.