SUSE-SU-2017:0292-1 Security update for dbus-1
Not scored
Published
Check this codebase for SUSE-SU-2017:0292-1 and fix it if it is affected.
What it is: SUSE-SU-2017:0292-1 is a memory corruption vulnerability in dbus-1, published on 26 Jan 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2017:0292-1 in the wild and no public exploit code.
Affected product: dbus-1. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/SUSE-SU-2017-0292-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2017-0292-1/index.md)
A format string vulnerability in D-Bus allows local attackers to execute arbitrary code or escalate privileges via crafted messages.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is SUSE-SU-2017:0292-1?
SUSE-SU-2017:0292-1 is a memory corruption vulnerability in dbus-1, published on 26 Jan 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
This update for dbus-1 to version 1.8.22 fixes one security issue and bugs.
The following security issue was fixed:
- bsc#1003898: Do not treat ActivationFailure message received from root-owned systemd name as a format string.
The following upstream changes are included:
- Change the default configuration for the session bus to only allow EXTERNAL authentication (secure kernel-mediated credentials-passing), as was already done for the system bus.
- Fix a memory leak when GetConnectionCredentials() succeeds (fdo#91008)
- Ensure that dbus-monitor does not reply to messages intended for others (fdo#90952)
- Add locking to DBusCounter's reference count and notify function (fdo#89297)
- Ensure that DBusTransport's reference count is protected by the corresponding DBusConnection's lock (fdo#90312)
- Correctly release DBusServer mutex before early-return if we run out of memory while copying authentication mechanisms (fdo#90021)
- Correctly initialize all fields of DBusTypeReader (fdo#90021)
- Fix some missing \n in verbose (debug log) messages (fdo#90004)
- Clean up some memory leaks in test code (fdo#90021)
Which versions are affected by SUSE-SU-2017:0292-1?
Linux distribution packages (10)
dbus-1 SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 1.8.22-24.2.1 |
dbus-1-x11 SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 1.8.22-24.2.1 |
dbus-1 SUSE:Linux Enterprise Server 12 SP2 | All versions | 1.8.22-24.2.1 |
dbus-1-x11 SUSE:Linux Enterprise Server 12 SP2 | All versions | 1.8.22-24.2.1 |
dbus-1 SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 1.8.22-24.2.1 |
dbus-1-x11 SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 1.8.22-24.2.1 |
dbus-1 SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 1.8.22-24.2.1 |
dbus-1-x11 SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 1.8.22-24.2.1 |
dbus-1 SUSE:Linux Enterprise Software Development Kit 12 SP2 | All versions | 1.8.22-24.2.1 |
dbus-1-x11 SUSE:Linux Enterprise Software Development Kit 12 SP2 | All versions | 1.8.22-24.2.1 |
How do I fix SUSE-SU-2017:0292-1?
Apply the vendor's patch.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is SUSE-SU-2017:0292-1 being exploited?
There is no known exploitation of SUSE-SU-2017:0292-1 in the wild and no public exploit code.