# CVE-2021-32000: clone-master-clean-up: dangerous file system operations

> Local attackers can delete arbitrary files via symlink following in the clone-master-clean-up script on SUSE Linux systems.

- **Severity:** Low 3.2 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 28 Jul 2021
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-54r8-8cq2-5p82, SUSE-SU-2022:3667-1, SUSE-SU-2022:3674-1, openSUSE-SU-2024:12840-1

## What is CVE-2021-32000?

CVE-2021-32000 is a low-severity path traversal vulnerability in Suse Linux Enterprise Server, published on 28 Jul 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A UNIX Symbolic Link (Symlink) Following vulnerability in the clone-master-clean-up.sh script of clone-master-clean-up in SUSE Linux Enterprise Server 12 SP3, SUSE Linux Enterprise Server 15 SP1; openSUSE Factory allows local attackers to delete arbitrary files. This issue affects: SUSE Linux Enterprise Server 12 SP3 clone-master-clean-up version 1.6-4.6.1 and prior versions. SUSE Linux Enterprise Server 15 SP1 clone-master-clean-up version 1.6-3.9.1 and prior versions. openSUSE Factory clone-master-clean-up version 1.6-1.4 and prior versions.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2021-32000?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `clone-master-clean-up` | SUSE:Linux Enterprise Module for Server Applications 15 SP3 | All versions | 1.8-150100.3.14.1 |
| `clone-master-clean-up` | SUSE:Linux Enterprise Module for Server Applications 15 SP4 | All versions | 1.8-150100.3.14.1 |
| `clone-master-clean-up` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 1.8-4.11.1 |
| `clone-master-clean-up` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 1.8-4.11.1 |
| `clone-master-clean-up` | openSUSE:Leap 15.3 | All versions | 1.8-150100.3.14.1 |
| `clone-master-clean-up` | openSUSE:Leap 15.4 | All versions | 1.8-150100.3.14.1 |
| `clone-master-clean-up` | openSUSE:Tumbleweed | All versions | 1.11-1.1 |

Products: Suse Linux Enterprise Server, Suse Opensuse Factory.

## How do I fix CVE-2021-32000?

Apply the vendor's patch.

## Is CVE-2021-32000 being exploited?

There is no known exploitation of CVE-2021-32000 in the wild and no public exploit code.

## Other vulnerabilities in Suse Linux Enterprise Server

- [CVE-2026-25702](https://insights.sbomify.com/CVE-2026-25702/): nftables disabled due to incorrect kernel backport (high 7.3)
- [CVE-2019-3687](https://insights.sbomify.com/CVE-2019-3687/): "easy" permission profile allows everyone execute dumpcap and read all network traffic (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-32000 and fix it if it is affected.

What it is: CVE-2021-32000 is a low-severity path traversal vulnerability in Suse Linux Enterprise Server, published on 28 Jul 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-32000 in the wild and no public exploit code.

Affected product: Suse Linux Enterprise 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/CVE-2021-32000/ (Markdown: https://insights.sbomify.com/CVE-2021-32000/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-32000
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-32000
- OSV: https://osv.dev/vulnerability/CVE-2021-32000

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