dbus-broker: dbus-broker is an implementation of a message bus as defined by the D-Bus specification
CVE-2022-31213 is fixed in 3 products on 1 platform, first by DEBIAN-CVE-2022-31213, released July 17, 2022. It is not reported as exploited. Patch Radar priority: High.
dbus-broker is an implementation of a message bus as defined by the D-Bus specification. Its aim is to provide high performance and reliability, while keeping compatibility to the D-Bus reference implementation. It is exclusively written for Linux systems, and makes use of many modern features provided by recent Linux kernel releases. Security Fix(es): * dbus-broker: a stack buffer over-read if a malicious Exec line is supplied (CVE-2022-31212) * dbus-broker: null pointer reference when supplying a malformed XML config file (CVE-2022-31213) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| dbus-broker · Debian 12.15 (bookworm) | 30-1 | DEBIAN-CVE-2022-31213 | Jul 17, 2022 |
| dbus-broker · Debian 13.5 (trixie) | 30-1 | DEBIAN-CVE-2022-31213 | Jul 17, 2022 |
| dbus-broker · Debian 14 | 30-1 | DEBIAN-CVE-2022-31213 | Jul 17, 2022 |
| dbus-broker · RHEL 9 | 0:28-5.1.el9_0 | RHSA-2022:6608 | Sep 20, 2022 |
| dbus-broker · almalinux 9 | 28-5.1.el9_0 | ALSA-2022:6608 | Sep 20, 2022 |
| dbus-broker · amzn 2023 | 32-1.amzn2023.0.2 | ALAS2023-2023-080 | Feb 17, 2023 |
| dbus-broker · ol 9 | 0:28-5.1.el9_0 | ELSA-2022-6608 | Sep 21, 2022 |
| dbus-broker · rocky 9 | 0:28-5.1.el9 | RLSA-2022:6608 | Sep 20, 2022 |
| dbus-broker-debuginfo · amzn 2023 | 32-1.amzn2023.0.2 | ALAS2023-2023-080 | Feb 17, 2023 |
| dbus-broker-debugsource · amzn 2023 | 32-1.amzn2023.0.2 | ALAS2023-2023-080 | Feb 17, 2023 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.