CVE-2018-6552
Last modified
CVE-2018-6552 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.39% chance of exploitation in the next 30 days.
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.
Metrics
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Apport Project | Apport | 2.14.1 |
| Apport Project | Apport | 2.20.9 |
| Apport Project | Apport | 2.20.7 |
| Apport Project | Apport | 2.20.1 |
References
- https://usn.ubuntu.com/3664-2/Vendor Advisory
- https://usn.ubuntu.com/usn/usn-3664-1Vendor Advisory
- https://usn.ubuntu.com/3664-2/Vendor Advisory
- https://usn.ubuntu.com/usn/usn-3664-1Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-6552?
How severe is CVE-2018-6552?
How do I fix CVE-2018-6552?
Are you affected by CVE-2018-6552?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
