dbcve.org
Unified Computing SystemApplication · Cisco

CVE-2019-1885

HIGH · 7.2 CVSS v3.1 Published 2019-08-21
Fix available
A fix is available. Upgrade to 3.0 / 4.0 or later.
See remediation →
78/100
Remediation priority · High
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
A vulnerability in the Redfish protocol of Cisco Integrated Management Controller (IMC) could allow an authenticated, remote attacker to inject and execute arbitrary commands with root privileges on an affected device. The vulnerability is due to insufficient validation of user-supplied input by the affected software. An attacker could exploit this vulnerability by sending crafted authenticated commands to the web-based management interface of the affected software. A successful exploit could allow the attacker to inject and execute arbitrary commands on an affected device with root privileges.

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

Command injection vulnerability in the Redfish protocol of Cisco Integrated Management Controller (IMC). An authenticated attacker can inject and execute arbitrary operating system commands with root privileges due to insufficient validation of user-supplied input in the web-based management interface.

MitigationApply the vendor-provided patch/update from Cisco for IMC. Until patched, restrict network access to the management interface to trusted networks and enforce strong authentication controls.

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
Unified Computing SystemApplication
Affected:= 4.0\(1c\)hs3
Integrated Management Controller SupervisorApplication
Affected:>= 3.0.0.0, < 3.0\(4k\)>= 4.0.0.0, < 4.0\(4b\)>= 4.0.0.0, < 4.0\(2f\)

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

CVSS:3.1/AV:N/AC:L/PR:H/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 IMC web management interface accessibility
    Check if TCP port 443 (HTTPS) or port 80 (HTTP) is open and reachable for the IMC management interface. Use a port scan or check network configuration: nmap -p 80,443 <target-ip> or verify in network infrastructure that the IMC GUI is externally or internally accessible.
    Affected if The IMC web-based management interface is exposed and reachable on the network (even if only internally).
  2. Determine IMC version
    Access the IMC web interface login page or use the Redfish API endpoint /redfish/v1/ to retrieve the ServiceRoot information which contains the firmware version. Alternatively, log into IMC and navigate to the Dashboard or BIOS/firmware information page to find the exact version string.
    Affected if The installed version matches: Cisco UCS = 4.0(1c)hs3, or IMC Supervisor: 3.0.0.0 through <3.0(4k), or 4.0.0.0 through <4.0(4b), or 4.0.0.0 through <4.0(2f).
  3. Verify Redfish service is enabled
    Check if the Redfish API endpoint responds by making an HTTP GET request to https://<imc-ip>/redfish/v1/ or /redfish. A successful response (HTTP 200) with JSON service root data indicates the Redfish service is active.
    Affected if The Redfish API endpoint is reachable and returns valid service information, indicating it is enabled and accessible.
  4. Confirm authentication capability
    Determine if you have valid IMC credentials or if default credentials may be in use. Attempt to authenticate to the web interface or Redfish API using available credentials to confirm the attack precondition.
    Affected if An attacker can obtain valid authentication credentials for the IMC management interface (whether through valid user accounts, default credentials, or credential compromise).

You are affected if your Cisco IMC runs an affected version (4.0(1c)hs3 for UCS, or IMC Supervisor versions 3.0.0.0 to <3.0(4k), 4.0.0.0 to <4.0(4b), or 4.0.0.0 to <4.0(2f)), the web management interface is network-accessible, and an authenticated session can be obtained to inject commands via the Redfish protocol.

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 3.0 / 4.0 or later
Fixed in 3.04.0
Interim mitigation

Apply the vendor-provided patch/update from Cisco for IMC. Until patched, restrict network access to the management interface to trusted networks and enforce strong authentication controls.

Fix this in Unified Computing System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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