CVE-2018-16866
What it is
An out of bounds read was discovered in systemd-journald in the way it parses log messages that terminate with a colon ':'. A local attacker can use this flaw to disclose process memory data. Versions from v221 to v239 are vulnerable.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. Limited direct impact.
- Exploit odds
- 1.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 1.1% in the next 30 days (EPSS).
- Severity: 3.3 LOW (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 1.1% · EPSS, next 30 days
- Weakness
- CWE-125 · Out-of-bounds read
- Record status
- Modified
Affected
- Systemd Project Systemd ≤ 239
- Debian Linux 9.0
- Canonical Ubuntu Linux 16.04
- Canonical Ubuntu Linux 18.04
- Canonical Ubuntu Linux 18.10
- Netapp Active Iq Performance Analytics Services
- Netapp Element Software
- Redhat Enterprise Linux 7.6
Attack profile CVSS 3.1 · 3.3
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2018-16866.md and follow it. Check whether this project is affected by CVE-2018-16866. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16866
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16866
References
- http://packetstormsecurity.com/files/152841/System-Down-A-systemd-journald-Exploit.html
- http://seclists.org/fulldisclosure/2019/May/21
- http://www.openwall.com/lists/oss-security/2019/05/10/4
- http://www.securityfocus.com/bid/106527
- https://access.redhat.com/errata/RHSA-2019:2091
- https://access.redhat.com/errata/RHSA-2019:3222
- https://access.redhat.com/errata/RHSA-2020:0593
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16866
- https://seclists.org/bugtraq/2019/May/25
- https://security.gentoo.org/glsa/201903-07
- https://security.netapp.com/advisory/ntap-20190117-0001/
- https://usn.ubuntu.com/3855-1/
- https://www.debian.org/security/2019/dsa-4367
- https://www.qualys.com/2019/01/09/system-down/system-down.txt
- http://packetstormsecurity.com/files/152841/System-Down-A-systemd-journald-Exploit.html
- http://seclists.org/fulldisclosure/2019/May/21
- http://www.openwall.com/lists/oss-security/2019/05/10/4
- http://www.securityfocus.com/bid/106527
- https://access.redhat.com/errata/RHSA-2019:2091
- https://access.redhat.com/errata/RHSA-2019:3222
- https://access.redhat.com/errata/RHSA-2020:0593
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16866
- https://seclists.org/bugtraq/2019/May/25
- https://security.gentoo.org/glsa/201903-07
- https://security.netapp.com/advisory/ntap-20190117-0001/