Bug 1120625 - (CVE-2018-16888) VUL-0: CVE-2018-16888: systemd: kills privileged process if unprivileged PIDFile was tampered
(CVE-2018-16888)
VUL-0: CVE-2018-16888: systemd: kills privileged process if unprivileged PIDF...
Status: RESOLVED DUPLICATE of bug 1065951
Classification: Novell Products
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents
unspecified
Other Other
: P3 - Medium : Normal
: ---
Assigned To: systemd maintainers
Security Team bot
https://smash.suse.de/issue/221983/
CVSSv3:SUSE:CVE-2018-16888:5.0:(AV:L...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-01-03 11:55 UTC by Karol Babioch
Modified: 2020-07-07 05:12 UTC (History)
4 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Karol Babioch 2019-01-03 11:55:17 UTC
systemd up to version 237 does not perform any check on the content of the PIDFile file of a service, which may result in systemd killing a process owned by other services when the service the PIDFile belongs to is stopped. In case the PIDFile is owned by unprivileged users (e.g. a service run with a different User field), systemd may kill privileged processes. A local attacker who is able to tamper with the PIDFile of a service may trick systemd into killing processes he would not have permissions to kill, in the moment a privileged user tries to kill the mentioned service.

Upstream patches:
https://github.com/systemd/systemd/pull/7816

Upstream issue:
https://github.com/systemd/systemd/issues/6632

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1662867
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-16888
Comment 1 Franck Bui 2019-01-09 08:50:04 UTC
That seems a duplicate of bsc#1065951 where we agreed to not fix SLE as the issue didn't seem critical enough...

What is the status now ?
Comment 3 Karol Babioch 2019-01-10 09:37:20 UTC
Marking as duplicate.

*** This bug has been marked as a duplicate of bug 1065951 ***