Ucs DirectorApplication · Cisco

CVE-2019-1938

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
A vulnerability in the web-based management interface of Cisco UCS Director and Cisco UCS Director Express for Big Data could allow an unauthenticated, remote attacker to bypass authentication and execute arbitrary actions with administrator privileges on an affected system. The vulnerability is due to improper authentication request handling. An attacker could exploit this vulnerability by sending crafted HTTP requests to an affected device. A successful exploit could allow an unprivileged attacker to access and execute arbitrary actions through certain APIs.

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

An authentication bypass vulnerability in the web-based management interface of Cisco UCS Director and Cisco UCS Director Express for Big Data allows unauthenticated, remote attackers to bypass authentication by sending specially crafted HTTP requests, granting administrator-level privileges to execute arbitrary actions through certain APIs.

MitigationApply the vendor-supplied patch or upgrade to a fixed version; if patches are unavailable, restrict network access to the management interface to trusted IPs only and implement aggressive monitoring for unauthorized administrative actions.

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.7.0.0= 6.7.1.0
Ucs Director Express For Big DataApplication
Affected:= 3.7.0.0= 3.7.1.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.0/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 if Cisco UCS Director is installed
    Check for Cisco UCS Director installation by looking for its management interface or checking installed packages/services on the system. Typically accessed via https://<hostname>/ucsd/
    Affected if The product is installed and running
  2. Determine the installed version of Cisco UCS Director
    Log into the web management interface and navigate to Admin > System > About, or check the version through the CLI if available. Look for version 6.7.0.0 or 6.7.1.0
    Affected if The installed version is exactly 6.7.0.0 or 6.7.1.0
  3. Identify if Cisco UCS Director Express for Big Data is installed
    Check for Cisco UCS Director Express for Big Data installation, typically accessed via https://<hostname>/bdc/ or similar endpoint
    Affected if The product is installed and running
  4. Determine the installed version of Cisco UCS Director Express for Big Data
    Log into the web management interface and navigate to the About or System Information page. Look for version 3.7.0.0 or 3.7.1.0
    Affected if The installed version is exactly 3.7.0.0 or 3.7.1.0
  5. Assess network exposure of the management interface
    Determine if the web-based management interface is accessible from untrusted networks. Check firewall rules and network ACLs protecting port 443/HTTPS for the UCS Director management endpoints
    Affected if The management interface is exposed to untrusted or public networks

You are affected if either Cisco UCS Director version 6.7.0.0 or 6.7.1.0, or Cisco UCS Director Express for Big Data version 3.7.0.0 or 3.7.1.0 is running AND the web management interface is network-accessible to untrusted users.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patch or upgrade to a fixed version; if patches are unavailable, restrict network access to the management interface to trusted IPs only and implement aggressive monitoring for unauthorized administrative actions.

Recommended fix Moderate confidence

Cisco UCS Director 6.7.2.0+ and Cisco UCS Director Express for Big Data 3.7.2.0+

  1. 1. Identify all affected Cisco UCS Director and Cisco UCS Director Express for Big Data instances in your environment (versions 6.7.0.0, 6.7.1.0, 3.7.0.0, 3.7.1.0)
  2. 2. Review the Cisco Security Advisory cisco-sa-20190515-ucs-auth-bypass on tools.cisco.com for the complete list of fixed releases
  3. 3. Plan maintenance window for upgrade - this is a critical authentication bypass vulnerability
  4. 4. Back up current configuration before upgrading
  5. 5. Upgrade Cisco UCS Director to version 6.7.2.0 or later
  6. 6. Upgrade Cisco UCS Director Express for Big Data to version 3.7.2.0 or later
  7. 7. After upgrade, verify the web-based management interface is accessible and functioning normally
  8. 8. Confirm the vulnerability is remediated by reviewing system logs and attempting the documented attack vector
Caveat Review Cisco release notes for any configuration or behavioral changes between 6.7.0.0/6.7.1.0 and 6.7.2.0+, and similarly for the Express version

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

Fix this in Ucs Director Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1938 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-1938 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