# SUSE-SU-2023:0002-1: Security update for sbd

> An update for sbd fixes startup synchronization issues and adds systemd hardening, preventing potential security bypasses in cluster environments.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Jan 2023

## What is SUSE-SU-2023:0002-1?

SUSE-SU-2023:0002-1 is a vulnerability in sbd, published on 2 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This update for sbd fixes the following issues:

Update to version 1.5.1+20221128.8ec8e01:

- sbd-inquisitor: fail startup if pacemaker integration is disabled while SBD_SYNC_RESOURCE_STARTUP is conflicting (bsc#1204319)
- sbd-inquisitor: do not warn about startup syncing if pacemaker integration is even intentionally disabled (bsc#1204319)
- sbd-inquisitor: log a warning if SBD_PACEMAKER is overridden by -P or -PP option (bsc#1204319)
- sbd-inquisitor: ensure a log info only tells the fact about how SBD_PACEMAKER is set (bsc#1204319)
- Added hardened to systemd service(s) (bsc#1181400).

## Which versions are affected by SUSE-SU-2023:0002-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sbd` | SUSE:Linux Enterprise High Availability Extension 15 SP4 | All versions | 1.5.1+20221128.8ec8e01-150400.3.3.1 |
| `sbd` | openSUSE:Leap 15.4 | All versions | 1.5.1+20221128.8ec8e01-150400.3.3.1 |

## How do I fix SUSE-SU-2023:0002-1?

Upgrade to a fixed version.

## Is SUSE-SU-2023:0002-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2023:0002-1 is a vulnerability in sbd, published on 2 Jan 2023. 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-2023:0002-1 in the wild and no public exploit code.

Affected product: sbd. 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-2023-0002-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2023-0002-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2023:0002-1

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