# CVE-2020-8028: salt-api is accessible to every user on SUSE Manager Server

> Local users can escalate to root on managed systems due to improper access control in salt-api configuration.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-pmmp-f225-r347, SUSE-SU-2020:2647-1, SUSE-SU-2020:2648-1

## What is CVE-2020-8028?

CVE-2020-8028 is a critical missing authorization vulnerability in SUSE Linux Enterprise Module for SUSE Manager Server 4.1, published on 17 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Improper Access Control vulnerability in the configuration of salt of SUSE Linux Enterprise Module for SUSE Manager Server 4.1, SUSE Manager Proxy 4.0, SUSE Manager Retail Branch Server 4.0, SUSE Manager Server 3.2, SUSE Manager Server 4.0 allows local users to escalate to root on every system managed by SUSE manager. On the managing node itself code can be executed as user salt, potentially allowing for escalation to root there. This issue affects: SUSE Linux Enterprise Module for SUSE Manager Server 4.1 google-gson versions prior to 2.8.5-3.4.3, httpcomponents-client-4.5.6-3.4.2, httpcomponents-. SUSE Manager Proxy 4.0 release-notes-susemanager-proxy versions prior to 4.0.9-0.16.38.1. SUSE Manager Retail Branch Server 4.0 release-notes-susemanager-proxy versions prior to 4.0.9-0.16.38.1. SUSE Manager Server 3.2 salt-netapi-client versions prior to 0.16.0-4.14.1, spacewalk-. SUSE Manager Server 4.0 release-notes-susemanager versions prior to 4.0.9-3.54.1.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `salt-netapi-client` | SUSE:Manager Server 3.2 | All versions | 0.16.0-4.14.1 |
| `spacewalk-admin` | SUSE:Manager Server 3.2 | All versions | 2.8.4.7-3.15.1 |
| `spacewalk-java` | SUSE:Manager Server 3.2 | All versions | 2.8.78.30-3.53.1 |
| `spacewalk-setup` | SUSE:Manager Server 3.2 | All versions | 2.8.7.11-3.28.1 |
| `google-gson` | SUSE:Manager Server Module 4.1 | All versions | 2.8.5-3.4.3 |
| `httpcomponents-client` | SUSE:Manager Server Module 4.1 | All versions | 4.5.6-3.4.2 |
| `httpcomponents-core` | SUSE:Manager Server Module 4.1 | All versions | 4.4.10-3.4.2 |
| `salt-netapi-client` | SUSE:Manager Server Module 4.1 | All versions | 0.17.0-3.3.2 |
| `spacewalk-admin` | SUSE:Manager Server Module 4.1 | All versions | 4.1.6-3.3.3 |
| `spacewalk-java` | SUSE:Manager Server Module 4.1 | All versions | 4.1.19-3.8.2 |
| `spacewalk-setup` | SUSE:Manager Server Module 4.1 | All versions | 4.1.6-3.3.2 |

Products: Suse Salt-Netapi-Client.

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

Apply the vendor's patch.

## Is CVE-2020-8028 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8028 is a critical missing authorization vulnerability in SUSE Linux Enterprise Module for SUSE Manager Server 4.1, published on 17 Sep 2020. 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-8028 in the wild and no public exploit code.

Affected product: SUSE Linux Enterprise Module for SUSE Manager Server 4.1. 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-8028/ (Markdown: https://insights.sbomify.com/CVE-2020-8028/index.md)
```

## Sources

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

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