Unified Computing SystemApplication · Cisco
CVE-2019-1634
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 Intelligent Platform Management Interface (IPMI) of Cisco Integrated Management Controller (IMC) could allow an authenticated, remote attacker to inject arbitrary commands that are executed with root privileges on the underlying operating system (OS). The vulnerability is due to insufficient input validation of user-supplied commands. An attacker who has administrator privileges and access to the network where the IPMI resides could exploit this vulnerability by submitting crafted input to the affected commands. A successful exploit could allow the attacker to gain root privileges on the 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's IPMI interface allows authenticated attackers with administrator privileges to inject and execute arbitrary OS commands with root privileges due to insufficient input validation of user-supplied commands.
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\(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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Cisco product running IMCLog into the Cisco UCS Manager or IMC Supervisor web interface or CLI and note the exact product name and model. Check the firmware or software version displayed in the system information or about section.Affected if The product is Cisco Unified Computing System or Cisco Integrated Management Controller Supervisor and the version matches the affected ranges (4.0(1c)hs3 for UCS; 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) or 4.0(2f) for IMC Supervisor).
-
Verify IPMI interface is enabledAccess the Cisco IMC web interface, navigate to the IPMI section under Server > Inventory > BMC Management or use the CLI command 'ipmi info' or 'show ipmi'. Confirm whether the IPMI over LAN or IPMI interface is actively enabled.Affected if IPMI interface is enabled and accessible over the network, making the command injection vector reachable.
-
Confirm administrator accounts existCheck the local user accounts in Cisco IMC under User Management or Administrator accounts. Verify if any administrator-level accounts are configured, either locally or via LDAP/RADIUS integration.Affected if At least one administrator-level account is configured in the IMC, which is required to exploit this vulnerability.
-
Check network accessibility of IPMIFrom a management network host, attempt to reach the IPMI UDP port 623 or check if the IPMI interface is bound to an accessible network interface. Review firewall or ACL rules that may allow or block IPMI traffic.Affected if The IPMI interface is reachable from a network where an attacker could potentially authenticate and inject commands.
A system is affected if it runs a vulnerable Cisco IMC version, has IPMI enabled, and has at least one administrator account configured with network access to the IPMI interface.
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
Restrict IPMI network access to trusted management networks and apply Cisco firmware updates that address this vulnerability.
Fix this in Unified Computing System
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1634 — 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-1634 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