dbcve.org
Unified Computing SystemApplication · Cisco

CVE-2019-1871

HIGH · 7.2 CVSS v3.0 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 Import Cisco IMC configuration utility of Cisco Integrated Management Controller (IMC) could allow an authenticated, remote attacker to cause a denial of service (DoS) condition and implement arbitrary commands with root privileges on an affected device. The vulnerability is due to improper bounds checking by the import-config process. An attacker could exploit this vulnerability by sending malicious packets to an affected device. When the packets are processed, an exploitable buffer overflow condition may occur. A successful exploit could allow the attacker to implement arbitrary code on the affected device with elevated 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

A buffer overflow vulnerability exists in the Import Cisco IMC configuration utility of Cisco Integrated Management Controller (IMC). The import-config process lacks proper bounds checking, allowing an authenticated remote attacker to send malicious packets that trigger a buffer overflow. Successful exploitation enables a denial of service condition and allows the attacker to execute arbitrary code with root privileges on the affected device.

MitigationApply the Cisco vendor firmware patch when available. As an interim control, restrict network access to the IMC management interface to only trusted administrative IPs and ensure IMC is not directly exposed to untrusted networks.

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\)

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.0/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 the Cisco IMC product type
    Access the IMC web interface or use CLI 'show version' to determine if the device runs Cisco Integrated Management Controller (IMC) Supervisor or Cisco Unified Computing System (UCS)
    Affected if The product is either Cisco IMC Supervisor or Cisco UCS version 4.0(1c)hs3
  2. Check Cisco UCS version
    From UCS Manager CLI, execute 'show version' or view the firmware version in the GUI under Admin > Firmware Management
    Affected if UCS Manager firmware version is exactly 4.0(1c)hs3
  3. Check Cisco IMC Supervisor version
    Log into IMC Supervisor web GUI, go to Admin > Software Management > Firmware Version, or use CLI 'show version'
    Affected if IMC Supervisor version is 3.0.0.0 through 3.0(4k-1) OR 4.0.0.0 through 4.0(4b-1)
  4. Verify import-config feature accessibility
    Confirm the configuration import utility is accessible by navigating to IMC Supervisor: Admin > Configuration Management > Import Configuration, or UCS: Server > Configuration > Import Configuration
    Affected if The import-config functionality is available and accessible to authenticated users
  5. Confirm IMC management interface is active
    Check that the IMC IP interface is configured and reachable. Use 'show ip interface' in IMC CLI or verify the management IP in the web GUI under Network > IPMI Settings
    Affected if IMC management interface is configured and operational

A system is affected if it runs Cisco UCS version 4.0(1c)hs3 or Cisco IMC Supervisor versions 3.0.0.0-3.0(4k-1) or 4.0.0.0-4.0(4b-1) and has the IMC import-config feature accessible to authenticated 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.

From vendor data
Upgrade available Upgrade to 3.0 / 4.0 or later
Fixed in 3.04.0
Interim mitigation

Apply the Cisco vendor firmware patch when available. As an interim control, restrict network access to the IMC management interface to only trusted administrative IPs and ensure IMC is not directly exposed to untrusted networks.

Fix this in Unified Computing System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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