Description
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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
The systemd Project systemd
through v240affected
References
- https://access.redhat.com/errata/RHSA-2019:0342 ↗
- https://lists.debian.org/debian-lts-announce/2019/01/msg00016.html ↗
- http://www.securityfocus.com/bid/106525 ↗
- https://www.debian.org/security/2019/dsa-4367 ↗
- https://access.redhat.com/errata/RHSA-2019:0204 ↗
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16865 ↗
- https://security.netapp.com/advisory/ntap-20190117-0001/ ↗
- https://www.qualys.com/2019/01/09/system-down/system-down.txt ↗
- https://usn.ubuntu.com/3855-1/ ↗
- https://access.redhat.com/errata/RHSA-2019:0049 ↗
- https://access.redhat.com/errata/RHSA-2019:0271 ↗
- https://access.redhat.com/errata/RHSA-2019:0361 ↗
- https://security.gentoo.org/glsa/201903-07 ↗
- https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html ↗
- https://access.redhat.com/errata/RHBA-2019:0327 ↗
- http://www.openwall.com/lists/oss-security/2019/05/10/4 ↗
- https://seclists.org/bugtraq/2019/May/25 ↗
- http://packetstormsecurity.com/files/152841/System-Down-A-systemd-journald-Exploit.html ↗
- http://seclists.org/fulldisclosure/2019/May/21 ↗
- https://access.redhat.com/errata/RHSA-2019:2402 ↗
- http://www.openwall.com/lists/oss-security/2021/07/20/2 ↗