Bug 167052 - CAN-2005-0201 - session bus does not restrict connections base on uid
Summary: CAN-2005-0201 - session bus does not restrict connections base on uid
Alias: None
Product: Fedora
Classification: Fedora
Component: dbus (Show other bugs)
(Show other bugs)
Version: 4
Hardware: All Linux
Target Milestone: ---
Assignee: John (J5) Palmieri
QA Contact:
Keywords: Security
Depends On:
TreeView+ depends on / blocked
Reported: 2005-08-29 20:44 UTC by John (J5) Palmieri
Modified: 2013-03-13 04:48 UTC (History)
2 users (show)

Fixed In Version: 0.33-3
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-05 05:54:23 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
FreeDesktop.org (Old) 2436 None None None Never

Description John (J5) Palmieri 2005-08-29 20:44:59 UTC
Description of problem:

If I login as root and create a session bus, then login as another user, I am
able to use dbus-send to connect to root's session bus.

To reproduce:
Login as root, open a terminal, echo $DBUS_SESSION_BUS_ADDRESS, write down the
Run dbus-monitor --session

Login as another user on a console, run:
env DBUS_SESSION_BUS_ADDRESS=(address written down above) dbus-send
--dest=org.freedesktop.DBus --type=method_call --print-reply
/org/freedesktop/DBus org.freedesktop.DBus.ListServices

The dbus-send gives a message about not being able to print the return value,
and the dbus-monitor on root's session bus shows the ListServices request coming

Comment 1 John (J5) Palmieri 2005-08-29 20:46:26 UTC
this is fgixed upstream nad waiting to be pushed for FC4

Comment 2 Fedora Update System 2005-08-30 03:25:37 UTC
From User-Agent: XML-RPC

dbus-0.33-3.fc4.1 has been pushed for FC4, which should resolve this issue.

If these problems are still present in this version, then please re-open this bug.

Note You need to log in before you can comment on or make changes to this bug.