The version of dbus installed on the remote host is prior to 1.10.24-7. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2022-1870 advisory.

  - dbus before 1.10.28, 1.12.x before 1.12.16, and 1.13.x before 1.13.12, as used in DBusServer in Canonical     Upstart in Ubuntu 14.04 (and in some, less common, uses of dbus-daemon), allows cookie spoofing because of     symlink mishandling in the reference implementation of DBUS_COOKIE_SHA1 in the libdbus library. (This only     affects the DBUS_COOKIE_SHA1 authentication mechanism.) A malicious client with write access to its own     home directory could manipulate a ~/.dbus-keyrings symlink to cause a DBusServer with a different uid to     read and write in unintended locations. In the worst case, this could result in the DBusServer reusing a     cookie that is known to the malicious client, and treating that cookie as evidence that a subsequent     client connection came from an attacker-chosen uid, allowing authentication bypass. (CVE-2019-12749)

  - An issue was discovered in dbus >= 1.3.0 before 1.12.18. The DBusServer in libdbus, as used in dbus-     daemon, leaks file descriptors when a message exceeds the per-message file descriptor limit. A local     attacker with access to the D-Bus system bus or another system service's private AF_UNIX socket could use     this to make the system service reach its file descriptor limit, denying service to subsequent D-Bus     clients. (CVE-2020-12049)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Amazon Linux 2 : dbus (ALAS-2022-1870)

high Nessus Plugin ID 167227

Version 1.2