# SUSE-SU-2025:0404-1: Security update for rsync

> SUSE updated rsync to protocol version 32 to indicate the server is patched against recent vulnerabilities, ensuring clients can verify security status.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 10 Feb 2025

## What is SUSE-SU-2025:0404-1?

SUSE-SU-2025:0404-1 is a vulnerability in rsync, published on 10 Feb 2025. It can be exploited over the network.

### Official description

This update for rsync fixes the following issues:

- Bump rsync protocol version to 32 to show server is patched against recent vulnerabilities.

## Which versions are affected by SUSE-SU-2025:0404-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rsync` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 3.2.7-150600.3.11.1 |
| `rsync` | openSUSE:Leap 15.6 | All versions | 3.2.7-150600.3.11.1 |

## How do I fix SUSE-SU-2025:0404-1?

Apply the vendor's patch.

## Is SUSE-SU-2025:0404-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2025:0404-1 is a vulnerability in rsync, published on 10 Feb 2025. It can be exploited over the network.
Exploitation: There is no known exploitation of SUSE-SU-2025:0404-1 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2025:0404-1

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