# CVE-2020-8029: skuba: Insecure handling of private key

> Local attackers can access the kubelet private key due to insecure file permissions in SUSE CaaS Platform.

- **Severity:** Low 2.9 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2021
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-3hfm-p6g2-9fv7

## What is CVE-2020-8029?

CVE-2020-8029 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, with no action from the victim.

### Official description

A Incorrect Permission Assignment for Critical Resource vulnerability in skuba of SUSE CaaS Platform 4.5 allows local attackers to gain access to the kublet key. This issue affects: SUSE CaaS Platform 4.5 skuba versions prior to https://github.com/SUSE/skuba/pull/1416.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Suse Caas Platform.

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

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

## Is CVE-2020-8029 being exploited?

There is no known exploitation of CVE-2020-8029 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-8030](https://insights.sbomify.com/CVE-2020-8030/): skuba: Insecure /tmp usage when joining node to cluster (low 3.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8029 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, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-8029 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-8029/ (Markdown: https://insights.sbomify.com/CVE-2020-8029/index.md)
```

## Sources

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

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