if reply.message_type == MessageType.ERROR: print(f"Standard property set failed: {reply.body[0]}") # Fallback to a known legacy method legacy_msg = Message( destination='org.bluez', path='/org/bluez/hci0', interface='org.bluez.AgentManager1', member='RegisterAgent', signature='os', body=['/org/bluez/hci0/my_agent', 'NoInputNoOutput'] ) await bus.call(legacy_msg) print("Registered legacy agent, now able to pair without consent.") asyncio.run(bluetooth_exploit())
<policy user="nobody"> <allow own="com.vulnerable.Service"/> <allow send_destination="com.vulnerable.Service"/> </policy> If the policy is too permissive (e.g., allow user="*" ), any unprivileged local user can interact with a root-owned service. Before writing exploits, you need reconnaissance. The standard tool is busctl (from systemd) or the older gdbus . Silent Reconnaissance As an unprivileged user, you can list all services on the system bus without any authentication: dbus-1.0 exploit
The vendor copied policy files from an old BlueZ version that trusted user="root" only, but they ran the Bluetooth daemon as root and forgot to add <deny user="*"/> for sensitive methods. The RegisterAgent method does not check if the caller has the CAP_NET_ADMIN capability. Part 5: Persistence and Lateral Movement Once you have D-Bus method execution on a privileged service, persistence becomes elegant. The Systemd Trap Systemd exposes org.freedesktop.systemd1.Manager on the system bus. A successful exploit chain can call: if reply
Introduction In the sprawling ecosystem of the Linux desktop and embedded systems, D-Bus is the circulatory system. It’s the inter-process communication (IPC) broker that allows your file manager to talk to your password manager, your media keys to control the player, and systemd to launch services on demand. Since its introduction with the dbus-1.0 protocol, it has become a universal constant on everything from GNOME to Automotive Grade Linux. Silent Reconnaissance As an unprivileged user, you can
busctl monitor --match "type='method_call',interface='org.freedesktop.DBus.Properties'" This captures any process trying to read properties of other services—a passive way to discover sensitive information flows. Let’s move from theory to actionable exploits. These are not CVEs but classes of vulnerability enabled by misconfiguration or legacy dbus-1.0 assumptions. Vector 1: The No-Authentication Backdoor (Legacy Services) Many early dbus-1.0 services assumed that being on the system bus implied trust. A classic example is com.ubuntu.SoftwareProperties . In older versions (pre-2020), it allowed any local user to enable or disable repositories, effectively granting the ability to install malicious packages after a social engineering reboot.
# Introspect the Bluetooth adapter introspection = await bus.introspect('org.bluez', '/org/bluez/hci0')