# SUSE-SU-2018:2181-1: Recommended update for yast2-ftp-server

> An attacker can exploit weak SSL protocols in the yast2-ftp-server configuration to bypass security measures.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Aug 2018

## What is SUSE-SU-2018:2181-1?

SUSE-SU-2018:2181-1 is a vulnerability in yast2-ftp-server, published on 3 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This update for yast2-ftp-server fixes the following issues:

Feature update:

fate#321043: Added additional searchkeys to desktop file.

Security issues fixed:

- bsc#921303: Drop SSLv2 and SSLv3 as it is dropped for security reason for vsftpd.

Bug fixes:

- bsc#1041829: Do not modify value when Browse dialog is canceled.

## Which versions are affected by SUSE-SU-2018:2181-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `yast2-ftp-server` | SUSE:Linux Enterprise Module for Basesystem 15 | All versions | 4.0.7-3.3.1 |

## How do I fix SUSE-SU-2018:2181-1?

Apply the vendor's patch.

## Is SUSE-SU-2018:2181-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2018:2181-1 is a vulnerability in yast2-ftp-server, published on 3 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2018:2181-1 in the wild and no public exploit code.

Affected product: yast2-ftp-server. 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-2018-2181-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2018-2181-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2018:2181-1

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