dbcve.org
Integrated Management Controller SupervisorApplication · Cisco

CVE-2017-6617

MEDIUM · 5.4 CVSS v3.0 Published 2017-04-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/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 session identification management functionality of the web-based GUI of Cisco Integrated Management Controller (IMC) 3.0(1c) could allow an unauthenticated, remote attacker to hijack a valid user session on an affected system. The vulnerability exists because the affected software does not assign a new session identifier to a user session when a user authenticates to the web-based GUI. An attacker could exploit this vulnerability by using a hijacked session identifier to connect to the software through the web-based GUI. A successful exploit could allow the attacker to hijack an authenticated user's browser session on the affected system. Cisco Bug IDs: CSCvd14583.

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

This is a session fixation vulnerability in Cisco IMC web-based GUI where the software fails to regenerate session identifiers upon successful user authentication. An attacker who obtains a valid session ID (e.g., through URL interception or prediction) can hijack the authenticated user's browser session because the same session ID is used before and after login. The attacker does not need credentials but relies on exploiting the predictable/known session ID.

MitigationApply the Cisco patch for CSCvd14583. Until patched, monitor for suspicious session usage and avoid exposing session identifiers in URLs or logs. Consider implementing application-layer session timeout as a compensating control.

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
Affected:= 3.0\(1c\)

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
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/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. Identify Cisco IMC Supervisor installation
    Locate and confirm the Cisco Integrated Management Controller Supervisor product is installed in your environment. This is typically deployed as a standalone appliance or virtual machine for managing Cisco UCS servers.
    Affected if The product is not installed, you are not affected by this CVE.
  2. Check installed version number
    Access the IMC Supervisor web interface or use CLI commands to determine the exact version. Navigate to the Admin section or use 'show version' command. Compare the version string to 3.0(1c).
    Affected if Your installed version is exactly 3.0(1c), indicating you are running the affected version.
  3. Confirm web-based GUI is enabled
    Verify that the IMC Supervisor web-based GUI interface is accessible and enabled. Check if HTTPS/HTTP access to the management interface is active.
    Affected if The web GUI is disabled and inaccessible, the attack surface is reduced though version check remains important.
  4. Review session handling configuration
    Examine any available session management settings or logs for session ID behavior. Look for evidence of session IDs appearing in URLs, cookies, or logs before and after authentication.
    Affected if Session IDs are reused across login boundaries (same ID before and after successful authentication), confirming the vulnerability is present.

You are affected if Cisco IMC Supervisor version 3.0(1c) is installed and the web-based GUI is accessible, as this version fails to regenerate session IDs after authentication.

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 patch for CSCvd14583. Until patched, monitor for suspicious session usage and avoid exposing session identifiers in URLs or logs. Consider implementing application-layer session timeout as a compensating control.

Fix this in Integrated Management Controller Supervisor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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