github-starred/firejail

Fork 0

mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00

[GH-ISSUE #855] Block access to dbus #585

New issue

Closed

opened 2026-05-05 06:13:13 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 06:13:13 -06:00

Owner

Originally created by @HulaHoopWhonix on GitHub (Oct 11, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/855

A very serious vulnerability was discovered where dbus-daemon used ipc message as format string. Subgraph's Oz sandbox say they are not affected since they block dbus access to isolated processes. I recommend you do the same if not already.

https://bugs.freedesktop.org/show_bug.cgi?id=98157

/cc @adrelanos

Originally created by @HulaHoopWhonix on GitHub (Oct 11, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/855 A very serious vulnerability was discovered where dbus-daemon used ipc message as format string. Subgraph's Oz sandbox say they are not affected since they block dbus access to isolated processes. I recommend you do the same if not already. https://bugs.freedesktop.org/show_bug.cgi?id=98157 /cc @adrelanos

gitea-mirror

2026-05-05 06:13:13 -06:00

closed this issue
added the
information_old
label

gitea-mirror commented

2026-05-05 06:13:19 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (Oct 11, 2016):

Easiest ways to do so:

Force DBus to use a standard UNIX socket (makes it easier to block) - see #801 for how to do so.
Only whitelist /tmp/dbus-socket when necessary.

@chiraag-nataraj commented on GitHub (Oct 11, 2016): Easiest ways to do so: 1) Force DBus to use a standard UNIX socket (makes it easier to block) - see #801 for how to do so. 2) Only whitelist /tmp/_dbus-socket_ when necessary.

gitea-mirror commented

2026-05-05 06:13:22 -06:00

Author

Owner

@netblue30 commented on GitHub (Oct 11, 2016):

In our case dbus can be disabled using a network namespace (--net) or AppAromr (--apparmor). It can also be disabled by configuring dbus to use a regular Unix socket instead of the abstract Unix socket, and blacklisting the socket inside the sandbox.

@netblue30 commented on GitHub (Oct 11, 2016): In our case dbus can be disabled using a network namespace (--net) or AppAromr (--apparmor). It can also be disabled by configuring dbus to use a regular Unix socket instead of the abstract Unix socket, and blacklisting the socket inside the sandbox.

gitea-mirror commented

2026-05-05 06:13:24 -06:00

Author

Owner

@intika commented on GitHub (Jul 29, 2018):

i am blocking dbus access to chrome just by giving it a fake dbus address
env DBUS_SESSION_BUS_ADDRESS=none firejail chrome

@intika commented on GitHub (Jul 29, 2018): i am blocking dbus access to chrome just by giving it a fake dbus address `env DBUS_SESSION_BUS_ADDRESS=none firejail chrome`

gitea-mirror commented

2026-05-05 06:13:28 -06:00

Author

Owner

@SkewedZeppelin commented on GitHub (Jul 29, 2018):

@intika there is a dedicated nodbus option available in Firejail 0.9.54 and higher. It is more effective when combined with net none and if available apparmor.

@SkewedZeppelin commented on GitHub (Jul 29, 2018): @intika there is a dedicated `nodbus` option available in Firejail 0.9.54 and higher. It is more effective when combined with `net none` and if available `apparmor`.

gitea-mirror referenced this issue

2026-05-05 10:05:48 -06:00

[PR #585] [MERGED] Proposed #3673

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#585

No description provided.

Rows
Columns