Unified Computing SystemApplication · Cisco
CVE-2019-1908
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) implementation of Cisco Integrated Management Controller (IMC) could allow an unauthenticated, remote attacker to view sensitive system information. The vulnerability is due to insufficient security restrictions imposed by the affected software. A successful exploit could allow the attacker to view sensitive information that belongs to other users. The attacker could then use this information to conduct additional attacks.
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 confidenceCVE-2019-1908 is an information disclosure vulnerability in Cisco Integrated Management Controller (IMC) IPMI implementation. An unauthenticated remote attacker can view sensitive system information belonging to other users due to insufficient security restrictions in the IPMI interface.
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
>= 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 firmware versionAccess the Cisco IMC web interface and navigate to the Firmware Management or Administration > Firmware Upgrade page to view the current firmware version. Alternatively, use CLI: 'show version' or 'ipmitool -I lanplus -H < IMC IP > -U admin -P <password> raw' to retrieve version info.Affected if The firmware version matches = 4.0(1c)hs3 for Cisco UCS, or falls within ranges >= 2.0.0.0 < 2.0(13o), >= 3.0.0.0 < 3.0(4k), >= 4.0.0.0 < 4.0(4b), or >= 4.0.0.0 < 4.0(2f) for IMC Supervisor.
-
Confirm IPMI interface is enabledIn Cisco IMC web interface, go to Administration > Services > IPMI Settings to verify if the IPMI over LAN service is enabled. Via CLI, use: 'ipmitool -I lanplus -H <IMC_IP> -U admin -P <password> channel info 1' or check via IMC API.Affected if IPMI over LAN is enabled and accessible to the network.
-
Verify IPMI network accessibilityCheck if UDP port 623 (IPMI) is open and listening on the IMC management interface using: 'nc -zvu <IMC_IP> 623' or 'nmap -sU -p 623 <IMC_IP>'. Review network ACLs or firewall rules to determine if the IPMI port is exposed to untrusted networks.Affected if Port 623 is reachable from an untrusted or external network segment.
You are affected if your Cisco IMC or IMC Supervisor firmware version falls within the specified vulnerable ranges AND the IPMI interface is enabled and network-accessible to untrusted users.
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 data2.03.04.0
Apply the Cisco IMC firmware update addressing this vulnerability. Until patched, restrict network access to the IPMI interface and monitor for unauthorized access attempts.
Fix this in Unified Computing System
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1908 — 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-1908 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