# SUSE-SU-2021:1560-1: Security update for drbd-utils

> SUSE released a security update for drbd-utils to harden binaries by making them position independent, improving system security posture.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 11 May 2021

## What is SUSE-SU-2021:1560-1?

SUSE-SU-2021:1560-1 is a vulnerability in drbd-utils, published on 11 May 2021. 

### Official description

This update for drbd-utils fixes the following issues:

- Hardening: Made all binaries position independent (bsc#1185132)

## Which versions are affected by SUSE-SU-2021:1560-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drbd-utils` | SUSE:Linux Enterprise High Availability Extension 15 SP1 | All versions | 9.6.0-6.15.1 |

## How do I fix SUSE-SU-2021:1560-1?

Apply the vendor's patch.

## Is SUSE-SU-2021:1560-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2021:1560-1 is a vulnerability in drbd-utils, published on 11 May 2021. 
Exploitation: There is no known exploitation of SUSE-SU-2021:1560-1 in the wild and no public exploit code.

Affected product: drbd-utils. 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-2021-1560-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2021-1560-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2021:1560-1

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