Firepower Extensible Operating SystemOperating system · Cisco
CVE-2015-6370
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 · uneditedThe Management I/O (MIO) component in Cisco Firepower Extensible Operating System 1.1(1.160) on Firepower 9000 devices allows local users to execute arbitrary OS commands as root via crafted CLI input, aka Bug ID CSCux10578.
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 confidenceThe Management I/O (MIO) component in Cisco Firepower Extensible Operating System 1.1(1.160) on Firepower 9000 devices contains a local privilege escalation vulnerability. An authenticated local user can execute arbitrary OS commands with root privileges by providing crafted CLI input to the MIO component.
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 SystemOperating system
= 1.1\(1.160\)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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
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 device modelExecute 'show version' or check the hardware label to confirm the device is Cisco Firepower 9000 seriesAffected if Device is not a Firepower 9000 appliance - not affected
-
Check the FXOS versionExecute 'show version' from the FXOS CLI or check via the management interface to determine if the installed version is exactly 1.1(1.160)Affected if Version is not 1.1(1.160) - not affected
-
Verify local authentication is enabledCheck if local user authentication is configured on the device via 'show running-config aaa' or by reviewing the authentication settings in the FXOS CLIAffected if Local authentication is disabled and only TACACS/RADIUS is used - likely not affected
-
Confirm MIO component accessVerify the Management I/O CLI interface is accessible by attempting to access the mio> or system prompt from the console or SSH sessionAffected if MIO CLI interface is not reachable - not affected
-
Check for existing local user accountsExecute 'show user-account' or review local user configuration to determine if any local users are configured on the systemAffected if No local user accounts exist - not affected
A user is affected only if they are running Cisco Firepower 9000 with FXOS version 1.1(1.160) and have local user accounts with access to the MIO CLI component.
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 dataApply the Cisco firmware update that addresses this vulnerability. Until patched, strictly limit physical and console access to the device and ensure only trusted personnel have local user accounts.
Fix this in Firepower Extensible Operating System
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2015-6370 — 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-2015-6370 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