systemd 240 Access Control shared/bus-util.c bus_open_system_watch_bind_with_description D-Bus Message access control

Summaryinfo

A vulnerability classified as critical has been found in systemd 240. Impacted is the function bus_open_system_watch_bind_with_description of the file shared/bus-util.c of the component Access Control. The manipulation as part of D-Bus Message leads to access control. This vulnerability is referenced as CVE-2019-15718. The attack can only be performed from a local environment. No exploit is available.

Detailsinfo

A vulnerability was found in systemd 240. It has been rated as critical. This issue affects the function bus_open_system_watch_bind_with_description of the file shared/bus-util.c of the component Access Control. The manipulation as part of a D-Bus Message leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

In systemd 240, bus_open_system_watch_bind_with_description in shared/bus-util.c (as used by systemd-resolved to connect to the system D-Bus instance), calls sd_bus_set_trusted, which disables access controls for incoming D-Bus messages. An unprivileged user can exploit this by executing D-Bus methods that should be restricted to privileged users, in order to change the system's DNS resolver settings.

The weakness was published 09/04/2019 (Website). The advisory is shared at lists.fedoraproject.org. The identification of this vulnerability is CVE-2019-15718 since 08/28/2019. The exploitation is known to be easy. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 12/11/2023). MITRE ATT&CK project uses the attack technique T1068 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• systemd

Version

• 240

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion