# CVE-2020-8030: skuba: Insecure /tmp usage when joining node to cluster

> Local attackers can exploit insecure temporary file usage to leak bootstrap tokens or modify cluster configuration files.

- **Severity:** Low 3.6 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **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:** No
- **Published:** 11 Feb 2021
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-h8q4-9ggw-gcm9

## What is CVE-2020-8030?

CVE-2020-8030 is a low-severity vulnerability in SUSE CaaS Platform 4.5, published on 11 Feb 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 Insecure Temporary File vulnerability in skuba of SUSE CaaS Platform 4.5 allows local attackers to leak the bootstrapToken or modify the configuration file before it is processed, leading to arbitrary modifications of the machine/cluster.

Weakness: CWE-377 (DEPRECATED: Insecure Temporary File)

## Which versions are affected by CVE-2020-8030?

It affects 1 product.


Products: Suse Caas Platform.

## How do I fix CVE-2020-8030?

No fix has been published for CVE-2020-8030 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-8030 being exploited?

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

## Other vulnerabilities in SUSE CaaS Platform 4.5

- [CVE-2019-3682](https://insights.sbomify.com/CVE-2019-3682/): Insecure API port exposed to all Master Node guest containers (high 8.4)
- [CVE-2020-8029](https://insights.sbomify.com/CVE-2020-8029/): skuba: Insecure handling of private key (low 2.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-8030 and fix it if it is affected.

What it is: CVE-2020-8030 is a low-severity vulnerability in SUSE CaaS Platform 4.5, published on 11 Feb 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-2020-8030 in the wild and no public exploit code.

Affected product: SUSE CaaS Platform 4.5. 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-2020-8030/ (Markdown: https://insights.sbomify.com/CVE-2020-8030/index.md)
```

## Sources

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

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