dbcve.org
Integrated Management Controller SupervisorApplication · Cisco

CVE-2017-6616

HIGH · 8.8 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 →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 GUI of Cisco Integrated Management Controller (IMC) 3.0(1c) could allow an authenticated, remote attacker to execute arbitrary code on an affected system. The vulnerability exists because the affected software does not sufficiently sanitize specific values that are received as part of a user-supplied HTTP request. An attacker could exploit this vulnerability by sending a crafted HTTP request to the affected software. A successful exploit could allow the attacker to execute arbitrary code with the privileges of the user on the affected system. Cisco Bug IDs: CSCvd14578.

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

A remote code execution vulnerability exists in Cisco IMC web-based GUI version 3.0(1c) due to insufficient sanitization of user-supplied HTTP request values. An authenticated attacker can send a crafted HTTP request to execute arbitrary code with the privileges of the authenticated user on the affected system.

MitigationApply the Cisco patch for CSCvd14578 by upgrading to a fixed version of Cisco IMC firmware. If patching is not immediately possible, restrict network access to the IMC management interface to trusted IP addresses only.

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

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

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

  1. Confirm Cisco IMC product
    Log into the Cisco IMC web interface or check the system firmware. Navigate to the IMC Summary or About page to verify the product is Cisco Integrated Management Controller (IMC).
    Affected if The product is not Cisco IMC or is a different product line.
  2. Identify IMC firmware version
    In the IMC web GUI, go to Admin > Summary or Help > About to view the firmware version. Alternatively, use the CLI: 'show version' or 'ucimec version'.
    Affected if The installed version is exactly 3.0(1c). Note that only this specific version is affected.
  3. Verify web-based GUI is enabled
    In the IMC web GUI, go to Admin > User Management > HTTP/SMTP or check the network settings. Verify if the web interface (HTTP/HTTPS) is enabled under Network > IPMI over LAN or Management Interface settings.
    Affected if The web-based GUI interface is enabled and accessible over the network.
  4. Check IMC network accessibility
    Verify the IMC management IP is reachable from network segments where attackers could send crafted HTTP requests. Review access control lists or firewall rules for the IMC management interface.
    Affected if The IMC web GUI is accessible from untrusted networks or the management interface is exposed.
  5. Confirm authentication is configured
    Check if local user accounts or external authentication (LDAP/RADIUS) is configured in IMC under Admin > User Management. Verify that authentication is required for web GUI access.
    Affected if The IMC accepts authenticated sessions - the vulnerability requires a valid authenticated user to send the crafted HTTP request.

You are affected if Cisco IMC Supervisor version 3.0(1c) is installed AND the web-based GUI is enabled and accessible, since the vulnerability requires both an authenticated session and the HTTP interface to be present.

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 CSCvd14578 by upgrading to a fixed version of Cisco IMC firmware. If patching is not immediately possible, restrict network access to the IMC management interface to trusted IP addresses only.

Fix this in Integrated Management Controller Supervisor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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