dbcve.org
Unified Computing SystemApplication · Cisco

CVE-2017-6597

HIGH · 7.8 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 →
80/100
Remediation priority · High
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 local-mgmt CLI command of the Cisco Unified Computing System (UCS) Manager, Cisco Firepower 4100 Series Next-Generation Firewall (NGFW), and Cisco Firepower 9300 Security Appliance could allow an authenticated, local attacker to perform a command injection attack. More Information: CSCvb61394 CSCvb86816. Known Affected Releases: 2.0(1.68) 3.1(1k)A. Known Fixed Releases: 92.2(1.101) 92.1(1.1658) 2.0(1.115).

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 command injection vulnerability in the local-mgmt CLI command of Cisco UCS Manager, Firepower 4100 Series NGFW, and Firepower 9300 Security Appliance. An authenticated local attacker can inject arbitrary commands through insufficient input validation in the CLI, potentially executing commands with elevated privileges.

MitigationApply the fixed software releases (92.2(1.101), 92.1(1.1658), or 2.0(1.115) depending on the product version) to remediate this vulnerability. Until patching is possible, strictly limit local access and monitor for suspicious CLI usage.

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:= 3.1\(1k\)a
Firepower Extensible Operating SystemOperating system
Affected:= 2.0\(1.68\)

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

CVSS:3.0/AV:L/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. Identify the installed product and version
    Run 'show version' or 'ucsmshow version' in the CLI to determine if the system is Cisco UCS Manager or Firepower Extensible Operating System, and note the exact version number
    Affected if The version is Cisco UCS Manager 3.1(1k)a or Firepower Extensible Operating System 2.0(1.68)
  2. Verify local-mgmt CLI command availability
    Attempt to access the local-mgmt CLI context using 'local-mgmt' command from the main CLI prompt
    Affected if The local-mgmt command is accessible from the current user context (authenticated access required)
  3. Check for command injection vectors in local-mgmt
    Review any custom scripts, configurations, or input fields within the local-mgmt CLI context for lack of input sanitization
    Affected if The local-mgmt CLI accepts unsanitized input that could be leveraged for command injection
  4. Confirm authentication status
    Verify that the current CLI session is authenticated (logged in) by checking session status or running 'who' command
    Affected if The attacker has valid authenticated access to the CLI (local privilege escalation scenario)

A system is affected if it runs Cisco UCS Manager version 3.1(1k)a or Firepower Extensible Operating System version 2.0(1.68), has the local-mgmt CLI command available, and an authenticated attacker can inject commands through unsanitized input in that CLI context.

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 fixed software releases (92.2(1.101), 92.1(1.1658), or 2.0(1.115) depending on the product version) to remediate this vulnerability. Until patching is possible, strictly limit local access and monitor for suspicious CLI usage.

Fix this in Unified Computing System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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