CVE-2018-6552

published 31 May 2018 · updated 17 Sep 2024

Apport treats the container PID as the global PID when /proc/<global_pid>/ is missing

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 2.20.1-0ubuntu2.18, 2.20.7-0ubuntu3.9, 2.20.9-0ubuntu7.1 and 1 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
<2.20.1-0ubuntu2.18, <2.20.7-0ubuntu3.9, <2.20.9-0ubuntu7.1, =2.14.1-0ubuntu3.28, >=2.20.1-0ubuntu2.15 <unspecified, >=2.20.7-0ubuntu3.7 <unspecified, >=2.20.8-0ubuntu4 <unspecified2.20.1-0ubuntu2.18, 2.20.7-0ubuntu3.9, 2.20.9-0ubuntu7.1, unspecified

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2018-6552 severity on Zeptric[![CVE-2018-6552](https://zeptric.io/badge/cve/CVE-2018-6552.svg)](https://zeptric.io/cve/CVE-2018-6552)