# SUSE-SU-2017:2109-1: Security update for tcmu-runner

> Local attackers can cause denial of service or information leaks in tcmu-runner via D-Bus method calls.

- **Severity:** Not scored
- **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:** Yes
- **Published:** 9 Aug 2017

## What is SUSE-SU-2017:2109-1?

SUSE-SU-2017:2109-1 is a denial of service vulnerability in tcmu-runner, published on 9 Aug 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This update for tcmu-runner fixes the following issues:

-  qcow handler opens up an information leak via the CheckConfig D-Bus method (bsc#1049491) 
-  glfs handler allows local DoS via crafted CheckConfig strings (bsc#1049485) 
-  UnregisterHandler dbus method in tcmu-runner daemon for non-existing handler causes denial of service (bsc#1049488) 
-  UnregisterHandler D-Bus method in tcmu-runner daemon for internal handler causes denial of service (bsc#1049489) 
-  Memory leaks can be triggered in tcmu-runner daemon by calling D-Bus method for (Un)RegisterHandler (bsc#1049490)

## Which versions are affected by SUSE-SU-2017:2109-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tcmu-runner` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 1.2.0-2.3.1 |
| `tcmu-runner` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 1.2.0-2.3.1 |
| `tcmu-runner` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 1.2.0-2.3.1 |

## How do I fix SUSE-SU-2017:2109-1?

Apply the vendor's patch.

## Is SUSE-SU-2017:2109-1 being exploited?

There is no known exploitation of SUSE-SU-2017:2109-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2017:2109-1 and fix it if it is affected.

What it is: SUSE-SU-2017:2109-1 is a denial of service vulnerability in tcmu-runner, published on 9 Aug 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:2109-1 in the wild and no public exploit code.

Affected product: tcmu-runner. 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-2109-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2017-2109-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2017:2109-1

---
From sbomify Insights: https://insights.sbomify.com/SUSE-SU-2017-2109-1/
Summaries are generated and may contain mistakes; the official description above is the record.