Firepower Extensible Operating SystemApplication · Cisco
CVE-2017-6600
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 · uneditedA vulnerability in the CLI 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: CSCvb61351 CSCvb61637. Known Affected Releases: 2.0(1.68) 3.1(1k)A. Known Fixed Releases: 92.2(1.101) 92.1(1.1645) 2.0(1.82) 1.1(4.136.
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 confidenceThis vulnerability allows an authenticated local attacker to perform command injection attacks through the CLI interface of Cisco UCS Manager, Firepower 4100 Series NGFW, and Firepower 9300 Security Appliance. The attacker exploits insufficient input validation in the CLI to inject and execute arbitrary operating system commands with elevated privileges.
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
Firepower Extensible Operating SystemApplication
= 2.0\(1.68\)
Unified Computing SystemApplication
= 3.1\(1k\)aCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Cisco productAccess the device CLI or management interface and run 'show version' to determine if the system is running Cisco Firepower Extensible Operating System or Cisco Unified Computing System (UCS)Affected if The product is Cisco Firepower Extensible Operating System or Cisco Unified Computing System
-
Check Firepower Extensible Operating System versionRun 'show version' in the CLI and locate the software version string (for example, look for a version in the format 2.0(x.xx))Affected if The installed version is exactly 2.0(1.68)
-
Check Cisco UCS Manager versionRun 'show version' in the UCS Manager CLI and locate the software version string (for example, look for version 3.1(1k)a)Affected if The installed version is exactly 3.1(1k)a
-
Verify CLI interface accessibilityConfirm that CLI access is enabled and accessible to local users (check with 'show running-config | include ip http' or similar management access commands)Affected if CLI interface is enabled and the system has local user accounts configured
The environment is affected if running Cisco Firepower Extensible Operating System version 2.0(1.68) or Cisco UCS Manager version 3.1(1k)a with the CLI interface accessible to authenticated local users.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to the known fixed releases (92.2(1.101), 92.1(1.1645), 2.0(1.82), or 1.1(4.136)) or later versions that address this vulnerability. Limit local access to trusted personnel and monitor CLI activity for signs of exploitation.
Fix this in Firepower Extensible Operating System
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2017-6600 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-6600 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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