A flaw was found in systemd-journald. An out-of-bounds read when parsing a crafted syslog message that could lead to information disclosure.
This vulnerability was introduced in systemd v221.
Name: Qualys Research Labs
Function syslog_parse_identifier() in journald-syslog.c file does not properly parse the log string in case it ends with a ":", returning a pointer beyond the original string's limits. A local attacker may use this flaw to get disclose systemd-journal process memory and get an information leak.
The flaw was introduced in:
It was fixed with:
RHEL 7.6 ships systemd v219, but commit ec5ff4445cca6a1d786b8da36cf6fe0acc0b94c8 was backported, thus making it vulnerable to this flaw as well.
This seems to be the same as https://github.com/systemd/systemd/issues/9829, fixed by https://github.com/systemd/systemd/commit/a6aadf4ae0. The provided reproducer does not work with git master.
This issue affects the versions of systemd as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having a security impact of Moderate. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.
Red Hat Virtualization Hypervisor and Management Appliance include vulnerable versions of systemd. However, since exploitation requires local access and impact is restricted to information disclosure, this flaw is rated as having a security issue of Low. Future updates may address this issue.
Created systemd tracking bugs for this issue:
Affects: fedora-all [bug 1664975]
Please update the ETA of RHEL7 systemd errata for this CVE.
Please update the ETA for RHEL7 systemd errata release.
In reply to comment #20:
> Please update the ETA for RHEL7 systemd errata release.
I'm transferring this needinfo to the analyst in charge of this.
We do not release updates on ETA for errata.
This issue has been addressed in the following products:
Red Hat Enterprise Linux 7
Via RHSA-2019:2091 https://access.redhat.com/errata/RHSA-2019:2091
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):