# CVE-2020-26943: Arbitrary Code Execution in blazar-dashboard

> A user with dashboard access can execute arbitrary code on the Horizon host via Python eval, leading to service compromise.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-939m-4xpw-v34v, PYSEC-2020-225

## What is CVE-2020-26943?

CVE-2020-26943 is a critical code injection vulnerability in n/a, published on 16 Oct 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in OpenStack blazar-dashboard before 1.3.1, 2.0.0, and 3.0.0. A user allowed to access the Blazar dashboard in Horizon may trigger code execution on the Horizon host as the user the Horizon service runs under (because the Python eval function is used). This may result in Horizon host unauthorized access and further compromise of the Horizon service. All setups using the Horizon dashboard with the blazar-dashboard plugin are affected.

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

7 open source packages ship an affected version, including blazar-dashboard. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `blazar-dashboard` | PyPI | All versions | 1.3.1, 2.0.1, 3.0.1 |
| `blazar-dashboard` | PyPI | All versions | 1.3.1 |
| `blazar-dashboard` | PyPI | All versions | 1.3.1 |
| `blazar-dashboard` | PyPI | From 2.0.0 | 2.0.1 |
| `blazar-dashboard` | PyPI | From 2.0.0 | 2.0.1 |
| `blazar-dashboard` | PyPI | From 3.0.0 | 3.0.1 |
| `blazar-dashboard` | PyPI | From 3.0.0 | 3.0.1 |

Products: Openstack Blazar-Dashboard.

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

Upgrade blazar-dashboard to a fixed version for your release line: 1.3.1, 2.0.1 or 3.0.1.

## Is CVE-2020-26943 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-26943 is a critical code injection vulnerability in n/a, published on 16 Oct 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-26943 in the wild and no public exploit code.

Affected packages and fixed versions:
- blazar-dashboard (PyPI): affected all versions; fixed in 1.3.1, 2.0.1, 3.0.1
- blazar-dashboard (PyPI): affected all versions; fixed in 1.3.1
- blazar-dashboard (PyPI): affected all versions; fixed in 1.3.1
- blazar-dashboard (PyPI): affected from 2.0.0; fixed in 2.0.1
- blazar-dashboard (PyPI): affected from 2.0.0; fixed in 2.0.1
- blazar-dashboard (PyPI): affected from 3.0.0; fixed in 3.0.1
- blazar-dashboard (PyPI): affected from 3.0.0; fixed in 3.0.1

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-26943/ (Markdown: https://insights.sbomify.com/CVE-2020-26943/index.md)
```

## Sources

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

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