CVE-2018-16865
Reported by redhat · Published January 11, 2019
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 journal socket. A local attacker, or a remote one if systemd-journal-remote is used, may use this flaw to crash systemd-journald or execute code with journald privileges. Versions through v240 are vulnerable.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| systemd-libs | Amazon Linux | 219-57.amzn2.0.7 |
| systemd-sysv | Amazon Linux | 219-57.amzn2.0.7 |
| systemd-journal-gateway | Amazon Linux | 219-57.amzn2.0.7 |
| libgudev1 | Amazon Linux | 219-57.amzn2.0.7 |
| libgudev1-devel | Amazon Linux | 219-57.amzn2.0.7 |
| systemd-networkd | Amazon Linux | 219-57.amzn2.0.7 |
| systemd-devel | Amazon Linux | 219-57.amzn2.0.7 |
| systemd-python | Amazon Linux | 219-57.amzn2.0.7 |
| systemd-resolved | Amazon Linux | 219-57.amzn2.0.7 |
| systemd | systemd_project | 240 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| The systemd Project | systemd | through v240 |
| amazon:2 | systemd-libs | 0 |
| amazon:2 | systemd-sysv | 0 |
| amazon:2 | systemd-journal-gateway | 0 |
| amazon:2 | libgudev1 | 0 |
| amazon:2 | libgudev1-devel | 0 |
| amazon:2 | systemd-networkd | 0 |
| amazon:2 | systemd-devel | 0 |
| amazon:2 | systemd-python | 0 |
| amazon:2 | systemd-resolved | 0 |
| The systemd Project | systemd | 0 |
| amazon:2 | systemd | 0 |
| arch | systemd | 0 |
| chainguard | py3-systemd | * |
Timeline
- Jan 7, 2019 CVE Published
- Jan 10, 2019 PoC Published
- Apr 14, 2021 EPSS Score (30 in total, the first dated here)
- Jun 2, 2025 CVE Updated
- Mar 6, 2026 Distribution Patch (8 in total, the first dated here)
- Mar 6, 2026 Security Advisory (12 in total, the first dated here)
- Sep 23, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2018-16865
vulnetix vdb fixes CVE-2018-16865
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2018-16865/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- RHSA-2019:0342 vendor-advisoryx_refsource_REDHAT
- [debian-lts-announce] 20190123 [SECURITY] [DLA 1639-1] systemd security update mailing-listx_refsource_MLIST
- 106525 vdb-entryx_refsource_BID
- DSA-4367 vendor-advisoryx_refsource_DEBIAN
- RHSA-2019:0204 vendor-advisoryx_refsource_REDHAT
- x_refsource_CONFIRM
- x_refsource_CONFIRM
- x_refsource_MISC
- USN-3855-1 vendor-advisoryx_refsource_UBUNTU
- RHSA-2019:0049 vendor-advisoryx_refsource_REDHAT
- RHSA-2019:0271 vendor-advisoryx_refsource_REDHAT
- RHSA-2019:0361 vendor-advisoryx_refsource_REDHAT
- GLSA-201903-07 vendor-advisoryx_refsource_GENTOO
- x_refsource_MISC
- RHBA-2019:0327 vendor-advisoryx_refsource_REDHAT
- [oss-security] 20190510 Re: System Down: A systemd-journald exploit mailing-listx_refsource_MLIST
- 20190513 Re: System Down: A systemd-journald exploit mailing-listx_refsource_BUGTRAQ
- x_refsource_MISC
- 20190513 Re: System Down: A systemd-journald exploit mailing-listx_refsource_FULLDISC
- RHSA-2019:2402 vendor-advisoryx_refsource_REDHAT
…and 1 more