Unified Computing SystemApplication · Cisco
CVE-2019-1850
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 · uneditedA vulnerability in the web-based management interface of Cisco Integrated Management Controller (IMC) Software could allow an authenticated, remote attacker to inject arbitrary commands that are executed with root privileges on an affected device. An attacker would need to have valid administrator credentials on the device. The vulnerability is due to insufficient validation of user-supplied input by the affected software. An attacker with elevated privileges could exploit this vulnerability by sending crafted commands to the administrative web management interface of the affected software. A successful exploit could allow the attacker to inject and execute arbitrary, system-level commands with root privileges on an affected device.
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 confidenceCommand injection vulnerability in Cisco IMC web-based management interface allows authenticated administrators to inject arbitrary system commands that execute with root privileges due to insufficient input validation.
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
= 4.0\(1c\)hs3
Integrated Management Controller SupervisorApplication
>= 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.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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco IMC presenceLog into the Cisco UCS Manager or IMC CLI and run 'show firmware' or 'show version' to confirm the Integrated Management Controller is present on Cisco UCS servers or CIMC hardware.Affected if System does not have Cisco IMC installed - not affected.
-
Retrieve IMC firmware versionIn IMC web UI, navigate to Admin > Firmware Management or use CLI command 'imccipli -s -r firmware-info' to obtain the exact IMC firmware version.Affected if Unable to retrieve version - cannot determine status.
-
Compare version against affected rangesCompare the installed IMC version to: 4.0(1c)hs3; or 3.0.0.0 through 3.0(3k); or 4.0.0.0 through 4.0(3f). Versions < 3.0(4k), < 4.0(4b), or = 4.0(1c)hs3 are affected.Affected if Version matches or falls within the listed affected ranges - vulnerable.
-
Verify web interface is accessibleConfirm the IMC web-based management interface (HTTPS on port 443) is enabled and reachable. Check via CLI: 'imccipli -s -r network-https' or review IMC Network settings in web UI.Affected if Web interface is disabled or blocked - exploitation is significantly harder but version still matters.
System is affected if it runs Cisco IMC with a firmware version matching 4.0(1c)hs3, or any version >= 3.0.0.0 but < 3.0(4k), or >= 4.0.0.0 but < 4.0(4b), and the web-based management interface is enabled.
Generated from the published advisory. Verify against your own configuration.
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 data3.04.0
Apply the Cisco patch/Software update for Cisco IMC. Until patched, restrict network access to the IMC management interface to trusted admin networks and ensure strong credential policies.
Fix this in Unified Computing System
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1850 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-1850 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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