Unified Computing SystemApplication · Cisco
CVE-2019-1900
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 server of Cisco Integrated Management Controller (IMC) could allow an unauthenticated, remote attacker to cause the web server process to crash, causing a denial of service (DoS) condition on an affected system. The vulnerability is due to insufficient validation of user-supplied input on the web interface. An attacker could exploit this vulnerability by submitting a crafted HTTP request to certain endpoints of the affected software. A successful exploit could allow an attacker to cause the web server to crash. Physical access to the device may be required for a restart.
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 confidenceCisco IMC web server suffers from insufficient input validation on certain endpoints. An unauthenticated remote attacker can submit crafted HTTP requests that crash the web server process, causing denial of service. Physical access may be required to restart the service.
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
>= 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 IMC product in useDetermine whether the system is running Cisco Unified Computing System (UCS) or Cisco Integrated Management Controller (IMC) Supervisor. Check the product model or system information accessible via CLI or web interface.Affected if The system is either Cisco UCS or Cisco IMC Supervisor
-
Check the installed software versionAccess the IMC CLI or web interface and retrieve the current firmware/software version. Compare your installed version to the affected ranges: for UCS, version 4.0(1c)hs3 is affected; for IMC Supervisor, versions 4.0.0.0 through 4.0(2f) are affected.Affected if Installed version matches the affected ranges for either product
-
Determine web server accessibilityIdentify whether the IMC web management interface (HTTPS/HTTP ports) is reachable from network segments that include untrusted or external systems. Review firewall rules, ACLs, or management network configuration.Affected if The IMC web interface is accessible from untrusted networks
A system is affected if it runs an affected product version (UCS 4.0(1c)hs3 or IMC Supervisor 4.0.0.0 to 4.0(2f)) and the IMC web interface is network-accessible to untrusted attackers.
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 data4.0
Apply Cisco's patch for this vulnerability when available. Until then, restrict network access to the IMC management interface using firewalls or ACLs to limit exposure to untrusted networks.
Fix this in Unified Computing System
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1900 — 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-1900 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