Hide Forgot
D-Bus upstream reports: "" By attaching the file descriptor of a D-Bus connection to a D-Bus message and sending that message via the dbus-daemon, a malicious process can create D-Bus connections that persist after the process that created them has terminated. This exacerbates various patterns of undesirable/abusive behaviour by making it impossible to terminate them by killing processes. This has been addressed by closing any connection that has incoming file descriptors queued for deserialization for more than a configurable timeout, defaulting to 2.5 minutes. "" It is believed that versions 1.3.0 and later are affected. Acknowledgements: Red Hat would like to thank D-Bus upstream for reporting this issue. Upstream acknowledges Alban Crequy as the original reporter.
Created attachment 936438 [details] initial upstream patch 1
Created attachment 936439 [details] initial upstream patch 2
Created attachment 936441 [details] initial upstream patch 3
Created attachment 936442 [details] initial upstream patch 4
Created dbus tracking bugs for this issue: Affects: fedora-all [bug 1142581]
Created mingw-dbus tracking bugs for this issue: Affects: fedora-all [bug 1142582] Affects: epel-7 [bug 1142583]
Public now: http://www.openwall.com/lists/oss-security/2014/09/16/9
dbus-1.6.28-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
dbus-1.8.12-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
dbus-1.6.28-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.