dbcve.org
Unified Computing SystemApplication · Cisco

CVE-2017-6604

MEDIUM · 6.1 CVSS v3.0 Published 2017-04-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 interface of Cisco Integrated Management Controller (IMC) Software could allow an unauthenticated, remote attacker to redirect a user to a malicious web page. This vulnerability affects the following Cisco products running Cisco IMC Software: Unified Computing System (UCS) B-Series M3 and M4 Blade Servers, Unified Computing System (UCS) C-Series M3 and M4 Rack Servers. More Information: CSCvc37931. Known Affected Releases: 3.1(2c)B.

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

Open redirect vulnerability in Cisco IMC web interface allows unauthenticated remote attackers to craft malicious URLs that redirect users to arbitrary external websites. The vulnerability exists in the redirection logic of the web interface for affected UCS B-Series and C-Series servers.

MitigationApply the vendor-supplied patch or upgrade to a fixed release of Cisco IMC Software. For 3.1(2c)B, obtain the corrected version from Cisco (reference CSCvc37931).

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
Affected:= 2.2\(8b\)= 3.0\(1c\)= 3.1\(2c\)b

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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

  1. Confirm Cisco IMC web interface is accessible
    Attempt to access the Cisco IMC web interface by navigating to the IP address or hostname of the UCS server on port 443 or 80. The IMC web interface typically listens on these ports.
    Affected if The web interface responds and is reachable over the network
  2. Identify Cisco IMC version from web interface
    Log into the Cisco IMC web interface and navigate to the Admin section, typically under 'About' or 'Server Summary' to view the IMC firmware version. The version format appears as shown (for example, 2.2(8b), 3.0(1c), or 3.1(2c)B).
    Affected if The displayed IMC version matches exactly 2.2(8b), 3.0(1c), or 3.1(2c)b
  3. Verify IMC version via CLI
    If CLI access is available, connect to the CIMC via SSH or serial console and run the command 'show version' or 'scope chassis' followed by 'show detail' to retrieve the IMC firmware version.
    Affected if The CLI-reported version matches exactly one of the affected versions: 2.2(8b), 3.0(1c), or 3.1(2c)b
  4. Confirm the open redirect is exploitable
    Craft a test URL using the IMC redirect parameter. Typical IMC login URL patterns include redirects; attempt a URL such as https://[IMC-IP]/ucsm/login.html?redirect=//example.com to see if the application redirects to an external domain without validation.
    Affected if The application redirects to the external domain specified in the redirect parameter, confirming the open redirect vulnerability is present

A system is affected if it runs Cisco IMC firmware version 2.2(8b), 3.0(1c), or 3.1(2c)b AND the web interface is accessible and responds to the open redirect test.

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 vendor-supplied patch or upgrade to a fixed release of Cisco IMC Software. For 3.1(2c)B, obtain the corrected version from Cisco (reference CSCvc37931).

Fix this in Unified Computing System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,620
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-6604 — 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-2017-6604 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