1. Ubuntu Security Notices
  2. USN-5448-1

USN-5448-1: ncurses vulnerabilities

Publication date

26 May 2022

Overview

Several security issues were fixed in ncurses.

Releases

Packages

  • ncurses - shared libraries for terminal handling (32-bit)

Details

It was discovered that ncurses was not properly checking array bounds
when executing the fmt_entry function, which could result in an
out-of-bounds write. An attacker could possibly use this issue to
execute arbitrary code. (CVE-2017-10684)

It was discovered that ncurses was not properly checking user input,
which could result in it being treated as a format argument. An
attacker could possibly use this issue to expose sensitive
information or to execute arbitrary code. (CVE-2017-10685)

It was discovered that ncurses was incorrectly performing memory
management operations and was not blocking access attempts to
illegal memory locations. An attacker could possibly use this issue
to cause a denial of service. (CVE-2017-11112, CVE-2017-13729,

It was discovered that ncurses was not properly checking array bounds
when executing the fmt_entry function, which could result in an
out-of-bounds write. An attacker could possibly use this issue to
execute arbitrary code. (CVE-2017-10684)

It was discovered that ncurses was not properly checking user input,
which could result in it being treated as a format argument. An
attacker could possibly use this issue to expose sensitive
information or to execute arbitrary code. (CVE-2017-10685)

It was discovered that ncurses was incorrectly performing memory
management operations and was not blocking access attempts to
illegal memory locations. An attacker could possibly use this issue
to cause a denial of service. (CVE-2017-11112, CVE-2017-13729,
CVE-2017-13730, CVE-2017-13731, CVE-2017-13732, CVE-2017-13733,
CVE-2017-13734)

It was discovered that ncurses was not properly performing checks
on pointer values before attempting to access the related memory
locations, which could lead to NULL pointer dereferencing. An
attacker could possibly use this issue to cause a denial of service.
(CVE-2017-11113)

It was discovered that ncurses was incorrectly handling loops in
libtic, which could lead to the execution of an infinite loop. An
attacker could possibly use this issue to cause a denial of service.
(CVE-2017-13728)

Update instructions

In general, a standard system update will make all the necessary changes.

Learn more about how to get the fixes.

The problem can be corrected by updating your system to the following package versions:

Ubuntu Release Package Version
16.04 xenial libx32ncurses5 –  6.0+20160213-1ubuntu1+esm1  
lib32ncursesw5 –  6.0+20160213-1ubuntu1+esm1  
lib32tinfo5 –  6.0+20160213-1ubuntu1+esm1  
libtinfo5 –  6.0+20160213-1ubuntu1+esm1  
lib64tinfo5 –  6.0+20160213-1ubuntu1+esm1  
lib32ncurses5 –  6.0+20160213-1ubuntu1+esm1  
ncurses-bin –  6.0+20160213-1ubuntu1+esm1  
lib64ncurses5 –  6.0+20160213-1ubuntu1+esm1  
libncurses5 –  6.0+20160213-1ubuntu1+esm1  
libncursesw5 –  6.0+20160213-1ubuntu1+esm1  
ncurses-base –  6.0+20160213-1ubuntu1+esm1  
libx32ncursesw5 –  6.0+20160213-1ubuntu1+esm1  
libx32tinfo5 –  6.0+20160213-1ubuntu1+esm1  
ncurses-term –  6.0+20160213-1ubuntu1+esm1  
14.04 trusty libx32ncurses5 –  5.9+20140118-1ubuntu1+esm1  
lib32ncursesw5 –  5.9+20140118-1ubuntu1+esm1  
lib32tinfo5 –  5.9+20140118-1ubuntu1+esm1  
libtinfo5 –  5.9+20140118-1ubuntu1+esm1  
lib64tinfo5 –  5.9+20140118-1ubuntu1+esm1  
lib32ncurses5 –  5.9+20140118-1ubuntu1+esm1  
ncurses-bin –  5.9+20140118-1ubuntu1+esm1  
lib64ncurses5 –  5.9+20140118-1ubuntu1+esm1  
libncurses5 –  5.9+20140118-1ubuntu1+esm1  
libncursesw5 –  5.9+20140118-1ubuntu1+esm1  
ncurses-base –  5.9+20140118-1ubuntu1+esm1  
libx32ncursesw5 –  5.9+20140118-1ubuntu1+esm1  
libx32tinfo5 –  5.9+20140118-1ubuntu1+esm1  
ncurses-term –  5.9+20140118-1ubuntu1+esm1  

Reduce your security exposure

Ubuntu Pro provides ten-year security coverage to 25,000+ packages in Main and Universe repositories, and it is free for up to five machines.

Get Ubuntu Pro

References

Have additional questions?

Talk to a member of the team ›