Apport treats the container PID as the global PID when /proc/<global_pid>/ is missing
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.20.9-0ubuntu7.1, 2.20.1-0ubuntu2.18, 2.20.7-0ubuntu3.9
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- n/a Apport
From 2.20.8-0ubuntu4; fixed in 2.20.9-0ubuntu7.1
- n/a Apport
From 2.20.1-0ubuntu2.15; fixed in 2.20.1-0ubuntu2.18
- n/a Apport
From 2.20.7-0ubuntu3.7; fixed in 2.20.7-0ubuntu3.9
- n/a Apport
2.14.1-0ubuntu3.28