docs/1_Architecture_Guides/1.2_Security_Blueprint/5_Platform/1.2.5.3_SystemBus.md

   1 ---
   2 edit_link: ''
   3 title: SystemBus
   4 origin_url: >-
   5   https://raw.githubusercontent.com/automotive-grade-linux/docs-sources/master/docs/security-blueprint/part-5/3-SystemBus.md
   6 ---
   7
   8 <!-- WARNING: This file is generated by fetch_docs.js using /home/boron/Documents/AGL/docs-webtemplate/site/_data/tocs/architecture/master/security_blueprint-security-blueprint-book.yml -->
   9
  10 # D-Bus
  11
  12 D-Bus is a well-known **IPC** (Inter-Process Communication) protocol (and
  13 daemon) that helps applications to talk to each other. The use of D-Bus is great
  14 because it allows to implement discovery and signaling.
  15
  16 The D-Bus session is by default addressed by environment variable
  17 `DBUS_SESSION_BUS_ADDRESS`. Using **systemd** variable `DBUS_SESSION_BUS_ADDRESS`
  18 is automatically set for user sessions. D-Bus usage is linked to permissions.
  19
  20 D-Bus has already had several [security issues](https://www.cvedetails.com/vulnerability-list/vendor_id-13442/D-bus-Project.html)
  21 (mostly **DoS** issues), to allow applications to keep talking to each other.
  22 It is important to protect against this type of attack to keep the system more
  23 stable.
  24
  25
  26 <!-- section-config -->
  27
  28 Domain          | Object         | Recommendations
  29 --------------- | -------------- | ------------------------------------
  30 Platform-DBus-1 | Security model | Use D-Bus as IPC.
  31 Platform-DBus-2 | Security model | Apply D-BUS security patches: [D-Bus CVE](https://www.cvedetails.com/vulnerability-list/vendor_id-13442/D-bus-Project.html)
  32
  33 <!-- end-section-config -->