SUSE-SU-2017:0695-1 Recommended update for dbus-1
Not scored
Published
Check this codebase for SUSE-SU-2017:0695-1 and fix it if it is affected.
What it is: SUSE-SU-2017:0695-1 is a path traversal vulnerability in dbus-1, published on 15 Mar 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:0695-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-0695-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2017-0695-1/index.md)
A symlink attack in the dbus-1 nonce-tcp transport allows local attackers to escalate privileges or execute code.
- 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:0695-1?
SUSE-SU-2017:0695-1 is a path traversal vulnerability in dbus-1, published on 15 Mar 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 fixes the following issues:
Security issues fixed:
- Symlink attack in nonce-tcp transport. (bsc#1025950)
- Symlink attack in unit tests. (bsc#1025951)
Bugfixes:
- Remove sysvinit script, not used under systemd. (bsc#974092)
Which versions are affected by SUSE-SU-2017:0695-1?
Linux distribution packages (18)
dbus-1 SUSE:Linux Enterprise Desktop 12 SP1 | All versions | 1.8.22-24.8.1 |
dbus-1-x11 SUSE:Linux Enterprise Desktop 12 SP1 | All versions | 1.8.22-24.8.1 |
dbus-1 SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 1.8.22-24.8.1 |
dbus-1-x11 SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 1.8.22-24.8.1 |
dbus-1 SUSE:Linux Enterprise Server 12 SP1 | All versions | 1.8.22-24.8.1 |
dbus-1-x11 SUSE:Linux Enterprise Server 12 SP1 | All versions | 1.8.22-24.8.1 |
dbus-1 SUSE:Linux Enterprise Server 12 SP2 | All versions | 1.8.22-24.8.1 |
dbus-1-x11 SUSE:Linux Enterprise Server 12 SP2 | All versions | 1.8.22-24.8.1 |
dbus-1 SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 1.8.22-24.8.1 |
dbus-1-x11 SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 1.8.22-24.8.1 |
dbus-1 SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 1.8.22-24.8.1 |
dbus-1-x11 SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 1.8.22-24.8.1 |
dbus-1 SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 1.8.22-24.8.1 |
dbus-1-x11 SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 1.8.22-24.8.1 |
dbus-1 SUSE:Linux Enterprise Software Development Kit 12 SP1 | All versions | 1.8.22-24.8.1 |
dbus-1-x11 SUSE:Linux Enterprise Software Development Kit 12 SP1 | All versions | 1.8.22-24.8.1 |
dbus-1 SUSE:Linux Enterprise Software Development Kit 12 SP2 | All versions | 1.8.22-24.8.1 |
dbus-1-x11 SUSE:Linux Enterprise Software Development Kit 12 SP2 | All versions | 1.8.22-24.8.1 |
How do I fix SUSE-SU-2017:0695-1?
Apply the vendor's patch.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is SUSE-SU-2017:0695-1 being exploited?
There is no known exploitation of SUSE-SU-2017:0695-1 in the wild and no public exploit code.