dbcve.org
Ucs DirectorApplication · Cisco

CVE-2020-3247

CRITICAL · 9.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 →
100/100
Remediation priority · Urgent
High EPSS Remotely reachable No privileges 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 · high confidence

Multiple vulnerabilities in the REST API of Cisco UCS Director and Cisco UCS Director Express for Big Data allow remote attackers to bypass authentication mechanisms and conduct directory traversal attacks, potentially enabling unauthorized administrative access and file system compromise.

MitigationApply Cisco-provided patches for CVE-2020-3247; until patched, restrict network access to the REST API interface to trusted IP addresses only.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 Cisco UCS Director installation
    Locate and verify the presence of Cisco UCS Director or Cisco UCS Director Express for Big Data in your environment. Check installed software inventory or product documentation.
    Affected if The product is installed and no patch has been applied.
  2. Check installed version number
    Retrieve the exact version of Cisco UCS Director or Cisco UCS Director Express for Big Data running in your environment. Compare 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.5.0.4, 6.6.0.0 for UCS Director; 3.7.3.0 and below for UCS Director Express for Big Data.
    Affected if The installed version matches one of the affected versions listed.
  3. Verify REST API accessibility
    Determine if the REST API interface is exposed to the network. Check firewall rules, access control lists, or network segmentation that permit access to the REST API port or endpoint.
    Affected if The REST API is reachable from untrusted networks or IP addresses.
  4. Confirm REST API is enabled
    Check whether the REST API service or module is enabled in the Cisco UCS Director configuration. Review product documentation for how to verify REST API status.
    Affected if The REST API is enabled and running.

You are affected if 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 below) is installed with the REST API enabled and accessible.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.7.3.0
Interim mitigation

Apply Cisco-provided patches for CVE-2020-3247; until patched, restrict network access to the REST API interface to trusted IP addresses only.

Recommended fix Moderate confidence

Cisco UCS Director 6.0.2.0 or later; Cisco UCS Director Express for Big Data 3.7.4.0 or later

  1. 1. Identify the exact Cisco UCS Director version currently installed by navigating to Administration > System Overview > Version Information in the web interface
  2. 2. Identify the exact Cisco UCS Director Express for Big Data version currently installed
  3. 3. Download and install the latest Cisco UCS Director version from Cisco (6.0.2.0 or later) or the appropriate fixed release as specified in Cisco advisory cisco-sa-ucsd-rest-8mBfbS2a
  4. 4. Download and install the latest Cisco UCS Director Express for Big Data version from Cisco (3.7.4.0 or later) or the appropriate fixed release as specified in the same advisory
  5. 5. After upgrade, verify the REST API authentication mechanisms are functioning correctly
  6. 6. Test directory traversal protections by attempting authorized API access only
  7. 7. Review Cisco release notes for any known issues with the upgrade
Caveat Review Cisco release notes for potential compatibility issues with existing integrations; may require API client updates if authentication mechanisms changed

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-3247 — 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-3247 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