Integrated Management Controller SupervisorApplication · Cisco
CVE-2019-1974
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 bypass user authentication and gain access as an administrative user. The vulnerability is due to insufficient request header validation during the authentication process. An attacker could exploit this vulnerability by sending a series of malicious requests to an affected device. An exploit could allow the attacker to gain full administrative access to 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 · moderate confidenceAuthentication bypass vulnerability in Cisco IMC Supervisor, UCS Director, and UCS Director Express for Big Data web-based management interfaces. The flaw is due to insufficient request header validation during the authentication process, allowing unauthenticated remote attackers to bypass authentication and gain full administrative access through a series of malicious HTTP requests.
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.0, <= 2.2.0.6= 2.1.0.0
Ucs DirectorApplication
>= 5.5.0.0, <= 5.5.0.2>= 6.0.0.0, <= 6.0.1.3>= 6.5.0.0, <= 6.5.0.3>= 6.6.0.0, <= 6.6.1.0>= 6.7.0.0, <= 6.7.2.0= 6.7\(1.1\)= 6.7\(2.0\)
Ucs Director Express For Big DataApplication
>= 2.1.0.0, <= 2.1.0.2>= 3.0.0.0, <= 3.0.1.3>= 3.5.0.0, <= 3.5.0.3>= 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 in useAccess the web-based management interface and look for the product name in the login page header, title bar, or about section. Common paths: /ucsd/ or /imc/ in the URL, or check the login page for 'Cisco UCS Director', 'Cisco IMC Supervisor', or 'Cisco UCS Director Express for Big Data' brandingAffected if The product is one of Cisco IMC Supervisor, UCS Director, or UCS Director Express for Big Data
-
Determine the installed software versionIn the web interface, navigate to Administration > System > Software Updates or Help > About. Alternatively, access the CLI and run 'show version' or 'ucsmctxr -v' depending on the product. Record the full version number including any build numbersAffected if The version cannot be determined or the web interface is accessible but version info is hidden
-
Compare version against affected ranges for Cisco IMC SupervisorIf the product is Cisco IMC Supervisor, check if version is 2.1.0.0 OR between 2.2.0.0 and 2.2.0.6 inclusive. These are the only affected versionsAffected if Version is 2.1.0.0 OR >= 2.2.0.0 AND <= 2.2.0.6
-
Compare version against affected ranges for Cisco UCS DirectorIf the product is Cisco UCS Director, check if version falls into ANY of these ranges: 5.5.0.0-5.5.0.2, 6.0.0.0-6.0.1.3, 6.5.0.0-6.5.0.3, 6.6.0.0-6.6.1.0, 6.7.0.0-6.7.2.0 OR equals exactly 6.7(1.1) or 6.7(2.0)Affected if Version matches any of the listed ranges or specific versions 6.7(1.1) or 6.7(2.0)
-
Compare version against affected ranges for Cisco UCS Director Express for Big DataIf the product is Cisco UCS Director Express for Big Data, check if version is between 2.1.0.0 and 2.1.0.2 inclusive, between 3.0.0.0 and 3.0.1.3 inclusive, between 3.5.0.0 and 3.5.0.3 inclusive, between 3.7.0.0 and 3.7.2.0 inclusive, or equals exactly 3.6.0.0 or 3.6.1.0Affected if Version matches any of the listed ranges or specific versions 3.6.0.0 or 3.6.1.0
-
Verify web management interface accessibilityConfirm the web-based management interface is reachable over HTTP/HTTPS from the network. Check if TCP ports 443, 8443, or the configured management port are open and accessible. This is required for the vulnerability to be exploitableAffected if The web management interface is exposed and the product version matches any affected range
The environment is affected if any of the three products is running a version that falls within the specified version ranges AND the web-based management interface is network-accessible.
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 Cisco-provided patches or software updates for the affected products. Restrict network access to management interfaces to trusted sources only until the patch can be applied.
Fix this in Integrated Management Controller Supervisor
Scoped from the published advisory
- Consultation3.0 h
- Implementation3.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,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1974 — 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-1974 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