Medium severity · published Jan 14, 2019
CVE-2018-16888
It was discovered systemd does not correctly check the content of PIDFile files before using it to kill processes
4.7
CVSS
0.3%
EPSS
No
On KEV
Description
It was discovered systemd does not correctly check the content of PIDFile files before using it to kill processes. When a service is run from an unprivileged user (e.g. User field set in the service file), a local attacker who is able to write to the PIDFile of the mentioned service may use this flaw to trick systemd into killing other services and/or privileged processes. Versions before v237 are vulnerable.
CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
None
Confidentiality
None
Integrity
None
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.3% · higher than 22% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
SY
systemd · The systemd Project
v237 · source: vendor, NVD
AI
Active IQ Performance Analytics Services · Netapp
All versions, or not specified · source: NVD
ES
Element Software · Netapp
All versions, or not specified · source: NVD
EL
Enterprise Linux · Redhat
7.0 · source: NVD
UL
Ubuntu Linux · Canonical
16.04; 18.04; 19.10 · source: NVD
Affected product
SY
systemd
The systemd Project
More from systemd
7.8
CVE-2018-16865
An allocation of memory without limits, that could result in the stack clashing with another memory region, was discovered in systemd-journald when many entries are sent to the…
7.8
CVE-2018-16864
An allocation of memory without limits, that could result in the stack clashing with another memory region, was discovered in systemd-journald when a program with long command…
3.3
CVE-2019-3815
A memory leak was discovered in the backport of fixes for CVE-2018-16864 in Red Hat Enterprise Linux
3.3
CVE-2018-16866
An out of bounds read was discovered in systemd-journald in the way it parses log messages that terminate with a colon ':'