dbcve.org
Integrated Management ControllerApplication · Cisco

CVE-2019-1632

HIGH · 8.0 CVSS v3.0 Published 2019-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable

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 · unedited
A vulnerability in the web-based management interface of Cisco Integrated Management Controller (IMC) could allow an authenticated, remote attacker to conduct a cross-site request forgery (CSRF) attack and perform arbitrary actions on an affected device. The vulnerability is due to insufficient CSRF protections for the web-based management interface of the affected device. An attacker could exploit this vulnerability by persuading a user to follow a malicious link. A successful exploit could allow the attacker to use a web browser and the privileges of the user to perform arbitrary actions 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 confidence

Cisco IMC contains a CSRF vulnerability where insufficient protections in the web-based management interface allow an authenticated attacker to trick a user into executing unintended actions via a malicious link. The attacker leverages the user's active session privileges to perform arbitrary operations on the affected device.

MitigationApply the Cisco firmware patch for CVE-2019-1632 when available; implement additional CSRF protections such as anti-CSRF tokens and SameSite cookie attributes at the application layer as a defense-in-depth measure.

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 ControllerApplication
Affected:all versions
Unified Computing SystemApplication
Affected:= 4.0\(1c\)hs3

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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Cisco IMC is deployed
    Access the device via SSH or console and run 'show version' or check the web UI footer for the IMC version information
    Affected if The device is running Cisco Integrated Management Controller (any version)
  2. Identify if Cisco UCS version 4.0(1c)hs3 is deployed
    Check the Cisco UCS Manager version via 'show version' command or in the web interface about section
    Affected if The device is running Cisco Unified Computing System version 4.0(1c)hs3
  3. Confirm web-based management interface is enabled
    Verify the IMC web interface is accessible by attempting to reach https://<imc-ip> in a browser or via CLI command 'show http-server'
    Affected if The web-based management interface is enabled and accessible
  4. Verify CSRF token implementation
    Inspect HTTP responses from the IMC web interface using browser developer tools or a proxy to check if anti-CSRF tokens are present in forms or headers
    Affected if No anti-CSRF tokens are found in web requests and SameSite cookie attributes are not set

A user is affected if they are running any version of Cisco IMC or Cisco UCS version 4.0(1c)hs3 with the web-based management interface enabled and without CSRF protections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Cisco firmware patch for CVE-2019-1632 when available; implement additional CSRF protections such as anti-CSRF tokens and SameSite cookie attributes at the application layer as a defense-in-depth measure.

Fix this in Integrated Management Controller Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1632 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-1632 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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