CVE-2018-6552

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

N/A
Published: May 31, 2018 at 10:00 PM UTC
Updated: June 17, 2026 at 02:02 AM UTC
2 products affected across 2 vendorsApportUbuntu Linux

Using Apport by N/A?

Get instant alerts when new vulnerabilities affect Apport - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.4%

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 2.20.1-0ubuntu2.15v ≥ 2.20.7-0ubuntu3.7v ≥ 2.20.8-0ubuntu4v < 2.20.1-0ubuntu2.18v < 2.20.7-0ubuntu3.9v < 2.20.9-0ubuntu7.12.14.12.14.1-0ubuntu3.282.20.12.20.1-0ubuntu2.152.20.72.20.7-0ubuntu3.72.20.8-0ubuntu42.20.9
Affected range stops below 2.20.1-0ubuntu2.18, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.20.7-0ubuntu3.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.20.9-0ubuntu7.1, so it looks safe — our inference, not a vendor statement
canonical-ubuntu-linux (environment)
80%
All versions

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (2)

Vendor Advisoryx_refsource_UBUNTU
https://usn.ubuntu.com/3664-2/
Vendor Advisoryx_refsource_UBUNTU
https://usn.ubuntu.com/usn/usn-3664-1

CVSS

Confidentiality
COMPLETE
Integrity
COMPLETE
Availability
COMPLETE
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card