First published: Thu May 31 2018(Updated: )
Apport does not properly handle crashes originating from a PID namespace allowing local users to create certain files as root which an attacker could leverage to perform a denial of service via resource exhaustion, possibly gain root privileges, or escape from containers. The is_same_ns() function returns True when /proc/<global pid>/ does not exist in order to indicate that the crash should be handled in the global namespace rather than inside of a container. However, the portion of the data/apport code that decides whether or not to forward a crash to a container does not always replace sys.argv[1] with the value stored in the host_pid variable when /proc/<global pid>/ does not exist which results in the container pid being used in the global namespace. This flaw affects versions 2.20.8-0ubuntu4 through 2.20.9-0ubuntu7, 2.20.7-0ubuntu3.7, 2.20.7-0ubuntu3.8, 2.20.1-0ubuntu2.15 through 2.20.1-0ubuntu2.17, and 2.14.1-0ubuntu3.28.
Credit: security@ubuntu.com security@ubuntu.com
Affected Software | Affected Version | How to fix |
---|---|---|
Apport Project Apport | =2.14.1 | |
Canonical Ubuntu Linux | =14.04 | |
Apport Project Apport | =2.20.9 | |
Canonical Ubuntu Linux | =18.04 | |
Apport Project Apport | =2.20.7 | |
Canonical Ubuntu Linux | =17.10 | |
Apport Project Apport | =2.20.1 | |
Canonical Ubuntu Linux | =16.04 | |
All of | ||
Apport Project Apport | =2.14.1 | |
Canonical Ubuntu Linux | =14.04 | |
All of | ||
Apport Project Apport | =2.20.9 | |
Canonical Ubuntu Linux | =18.04 | |
All of | ||
Apport Project Apport | =2.20.7 | |
Canonical Ubuntu Linux | =17.10 | |
All of | ||
Apport Project Apport | =2.20.1 | |
Canonical Ubuntu Linux | =16.04 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.