CVE-2020-26943
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe blazar-dashboard Horizon plugin uses Python's eval() function insecurely, allowing any user with access to the Blazar dashboard to execute arbitrary code on the Horizon host as the service user account.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.3.1= 2.0.0= 3.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if blazar-dashboard package is installedRun 'pip show blazar-dashboard' or 'pip list | grep blazar' on the Horizon host to see if the package existsAffected if The package is not installed or cannot be found, then not affected; if installed, proceed to version check
-
Determine installed blazar-dashboard versionRun 'pip show blazar-dashboard' and note the Version field, or check via package manager (rpm -q python-blazar-dashboard or dpkg -l python-blazar-dashboard)Affected if Version is less than 1.3.1, or equals 2.0.0, or equals 3.0.0, then vulnerable to arbitrary code execution via eval()
-
Verify Horizon plugin is enabledCheck Horizon settings (local_settings.py) or the enabled plugins configuration for 'blazar' in the INSTALLED_APPS or HORIZON_CONFIG entriesAffected if The blazar dashboard plugin is listed in enabled Horizon plugins, making the eval() vulnerability accessible to dashboard users
-
Locate vulnerable eval() usage in blazar codeSearch the blazar-dashboard installation directory for 'eval(' usage, typically in horizon plugin views or forms; example: grep -r 'eval(' /path/to/blazar-dashboard/Affected if Code containing eval() is present and reachable through the Horizon web interface
User is affected if blazar-dashboard is installed and enabled in Horizon AND the installed version is < 1.3.1, = 2.0.0, or = 3.0.0.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.3.1
Upgrade blazar-dashboard to version 1.3.1, 2.0.0, 3.0.0 or later to remove the insecure eval() usage.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26943 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-26943 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data