Integrated Management Controller SupervisorApplication · Cisco
CVE-2019-12634
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) Supervisor, Cisco UCS Director, and Cisco UCS Director Express for Big Data could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition. The vulnerability is due to a missing authentication check in an API call. An attacker who can send a request to an affected system could cause all currently authenticated users to be logged off. Repeated exploitation could cause the inability to maintain a session in the web-based management portal.
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 confidenceThis vulnerability in Cisco IMC Supervisor, UCS Director, and UCS Director Express for Big Data stems from a missing authentication check in an API call. An unauthenticated remote attacker can send specially crafted requests that force all currently authenticated users to be logged off, causing denial of service. Repeated exploitation prevents users from maintaining sessions in the web management portal.
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
Integrated Management Controller SupervisorApplication
>= 2.2.0.3, <= 2.2.0.6
Ucs DirectorApplication
>= 6.7.0.0, <= 6.7.2.0= 6.6.0.0= 6.6.1.0
Ucs Director Express For Big DataApplication
>= 3.7.0.0, <= 3.7.2.0= 3.6.0.0= 3.6.1.0CVSS 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 installed Cisco management productDetermine which Cisco product is running: IMC Supervisor, UCS Director, or UCS Director Express for Big Data. Check the product name in the web management interface or system documentation.Affected if The product is one of the three affected products listed.
-
Check the installed product versionLocate the version number in the product's web interface (typically under About or System Information) or via CLI command. Compare it to the affected ranges: IMC Supervisor 2.2.0.3 to 2.2.0.6; UCS Director 6.6.0.0, 6.6.1.0, or 6.7.0.0 to 6.7.2.0; UCS Director Express for Big Data 3.6.0.0, 3.6.1.0, or 3.7.0.0 to 3.7.2.0.Affected if The installed version falls within any of the affected version ranges.
-
Verify web management interface accessibilityDetermine if the product's web-based management interface is reachable from the network. This is typically on ports 80, 443, or 8080. Check firewall rules and network exposure.Affected if The web management portal is exposed to network-accessible attackers.
-
Review authentication logs for session terminationsExamine the product's audit or security logs for sudden mass session logout events, especially from unauthenticated source IPs. Look for patterns of forced disconnections.Affected if Logs show unexpected mass session terminations without legitimate administrative action.
A user is affected if they have IMC Supervisor version 2.2.0.3-2.2.0.6, UCS Director version 6.6.0.0/6.6.1.0/6.7.0.0-6.7.2.0, or UCS Director Express for Big Data version 3.6.0.0/3.6.1.0/3.7.0.0-3.7.2.0, with the web management interface exposed to the network.
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 dataApply the vendor patch from Cisco to address the missing authentication check in the affected products. If no patch is available, consider network segmentation to limit exposure to unauthenticated attackers.
Fix this in Integrated Management Controller Supervisor
Scoped from the published advisory
- Consultation4.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12634 — 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-12634 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