# CVE-2020-28901: Command injection in n/a

> Attackers can execute arbitrary commands as root via corrupt component installation in Nagios Fusion, leading to full system compromise.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 May 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6cgq-hfg3-f2qv

## What is CVE-2020-28901?

CVE-2020-28901 is a critical command injection vulnerability in n/a, published on 24 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Command Injection in Nagios Fusion 4.1.8 and earlier allows for Privilege Escalation or Code Execution as root via vectors related to corrupt component installation in cmd_subsys.php.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 1 product.


Products: Nagios Fusion.

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

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

## Is CVE-2020-28901 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-28900](https://insights.sbomify.com/CVE-2020-28900/): Code injection in n/a (critical 9.8)
- [CVE-2020-28902](https://insights.sbomify.com/CVE-2020-28902/): Command injection in n/a (critical 9.8)
- [CVE-2020-28904](https://insights.sbomify.com/CVE-2020-28904/): Privilege escalation in n/a (critical 9.8)
- [CVE-2020-28907](https://insights.sbomify.com/CVE-2020-28907/): Security feature bypass in n/a (critical 9.8)
- [CVE-2020-28908](https://insights.sbomify.com/CVE-2020-28908/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-28901 is a critical command injection vulnerability in n/a, published on 24 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-28901 in the wild and no public exploit code.

Affected product: n/a. 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-28901/ (Markdown: https://insights.sbomify.com/CVE-2020-28901/index.md)
```

## Sources

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

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