Skip to content
Fencer Vulns
low 3.2

CVE-2021-32000 json

clone-master-clean-up: dangerous file system operations

published 2021-07-28 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-18870

cvss
3.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 22%
public exploits
0
none known

Summary

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.

Patch / fix

  • clone-master-clean-up SLES for SAP 12 SP5, SLES 12 SP5 1.8-4.11.1
  • clone-master-clean-up SLE Module for Server Applications 15 SP4, SLE Module for Server Applications 15 SP3, openSUSE Leap 15.4 +1 more 1.8-150100.3.14.1

suse advisories SUSE-SU-2022:3674-1SUSE-SU-2022:3667-1

  • clone-master-clean-up openSUSE Tumbleweed 1.11-1.1

opensuse advisories openSUSE-SU-2024:12840-1

Exploit prediction

0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • bugzilla.suse.com https://bugzilla.suse.com/show_bug.cgi?id=1181050 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 3.2 CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
NVD 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
NVD 2.0 6.6 AV:L/AC:L/Au:N/C:N/I:C/A:C

Affected products

  • SUSE SUSE Linux Enterprise Server 12 SP3
  • SUSE SUSE Linux Enterprise Server 15 SP1
  • openSUSE Factory

Classification

Weakness
  • CWE-59 Improper Link Resolution Before File Access

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.