Unified Computing SystemApplication · Cisco
CVE-2019-1865
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. The vulnerability is due to insufficient validation of user-supplied input by the affected software. An attacker could exploit this vulnerability by invoking an interface monitoring mechanism with a crafted argument on 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 remote attackers to execute arbitrary system commands with root privileges via insufficiently validated user input in an interface monitoring mechanism.
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
>= 1.5.0.0, < 1.5\(9g\)>= 2.0.0.0, < 2.0\(13o\)>= 3.0.0.0, < 3.0\(4k\)>= 4.0.0.0, < 4.0\(4b\)>= 4.0.0.0, < 4.0\(1d\)>= 4.0.0.0, < 4.0\(2c\)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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 web interface statusAccess the Cisco IMC web-based management interface login page (typically https://<server-ip>/) or check if port 443/80 is listening for IMC management. Use command: netstat -an | grep -E ':(80|443)\s' or check your server's open ports.Affected if The web-based management interface is accessible and running on the affected system.
-
Determine Cisco IMC software versionLog into Cisco IMC via CLI (ssh <ip>) and run: imc_version or show version. Alternatively, via web UI navigate to Admin > Firmware Management > Firmware Inventory to view installed firmware version.Affected if The installed version matches one of the affected ranges: 4.0(1c)hs3; 1.5.0.0 to <1.5(9g); 2.0.0.0 to <2.0(13o); 3.0.0.0 to <3.0(4k); 4.0.0.0 to <4.0(4b); 4.0.0.0 to <4.0(1d); 4.0.0.0 to <4.0(2c).
-
Verify interface monitoring feature is in useIn the web UI, navigate to the interface monitoring or network interface status pages. This is where the insufficiently validated user input occurs. Check for any user-defined interface names or monitoring parameters.Affected if The interface monitoring mechanism is configured or accessible to authenticated users.
-
Review system logs for suspicious command executionCheck Cisco IMC logs for unusual commands. In CLI run: scope logging, then show log. Look for commands containing shell metacharacters (;, |, &, $) or unexpected binary executions.Affected if Logs show execution of arbitrary commands not initiated by legitimate administrators, or commands containing injection patterns.
The system is affected if it runs a Cisco IMC version within the listed affected ranges AND has the web-based management interface enabled, as the command injection occurs through authenticated access to the interface monitoring mechanism.
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 data1.52.03.0
Apply the vendor-supplied patch/update for Cisco IMC Software. Restrict access to the web-based management interface to trusted networks or use jump hosts.
Fix this in Unified Computing System
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1865 — 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-1865 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