dbcve.org
Ucs DirectorApplication · Cisco

CVE-2020-3239

HIGH · 8.8 CVSS v3.1 Published 2020-04-15
Fix available
A fix is available. Upgrade to after 3.7.3.0 or later.
See remediation →
94/100
Remediation priority · Urgent
High EPSS Remotely reachable Zero-click

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 · unedited
Multiple vulnerabilities in the REST API of Cisco UCS Director and Cisco UCS Director Express for Big Data may allow a remote attacker to bypass authentication or conduct directory traversal attacks on an affected device. For more information about these vulnerabilities, see the Details section of this advisory.

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 · moderate confidence

This CVE describes authentication bypass and directory traversal vulnerabilities in the REST API of Cisco UCS Director and Cisco UCS Director Express for Big Data. A remote attacker can exploit these flaws to bypass authentication mechanisms or traverse directories on the affected system, potentially gaining unauthorized access to sensitive files or functionality.

MitigationApply the vendor-provided patch or update to the affected Cisco UCS Director versions. If immediate patching is not possible, restrict network access to the REST API interface and monitor for unauthorized access attempts.

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
Ucs DirectorApplication
Affected:= 6.0.0.0= 6.0.0.1= 6.0.1.0= 6.0.1.1= 6.0.1.2= 6.0.1.3= 6.5.0.0= 6.5.0.1= 6.5.0.2= 6.5.0.3= 6.5.0.4= 6.6.0.0
Ucs Director Express For Big DataApplication
Affected:<= 3.7.3.0

CVSS 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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Cisco UCS product
    Locate the installed Cisco UCS Director or Cisco UCS Director Express for Big Data application and determine which product is deployed in your environment.
    Affected if The product is Cisco UCS Director or Cisco UCS Director Express for Big Data.
  2. Check installed version of Cisco UCS Director
    Use the product's administration interface or system information command to retrieve the installed version number. Compare it against the affected versions: 6.0.0.0, 6.0.0.1, 6.0.1.0, 6.0.1.1, 6.0.1.2, 6.0.1.3, 6.5.0.0, 6.5.0.1, 6.5.0.2, 6.5.0.3, 6.6.0.0.
    Affected if The installed version matches any of the listed affected versions.
  3. Check installed version of Cisco UCS Director Express for Big Data
    Use the product's administration interface or system information command to retrieve the installed version number. Compare it against the affected range of versions 3.7.3.0 and lower.
    Affected if The installed version is 3.7.3.0 or lower.
  4. Verify REST API exposure
    Determine whether the REST API interface is enabled and exposed to network access. Check the product configuration settings for REST API service status and network binding. Review firewall or network access controls to determine if the REST API port is accessible from external or untrusted networks.
    Affected if The REST API is enabled and accessible from network segments outside the trusted administration zone.

You are affected if you have Cisco UCS Director (versions 6.0.0.0 through 6.6.0.0) or Cisco UCS Director Express for Big Data (version 3.7.3.0 or lower) with the REST API enabled and exposed on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 3.7.3.0
Interim mitigation

Apply the vendor-provided patch or update to the affected Cisco UCS Director versions. If immediate patching is not possible, restrict network access to the REST API interface and monitor for unauthorized access attempts.

Fix this in Ucs Director Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-3239 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-3239 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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