dbcve.org
Firepower Extensible Operating SystemOperating system · Cisco

CVE-2015-6435

CRITICAL · 9.8 CVSS v3.0 Published 2016-01-22
No fix yet
No fix has been published. The vendor has not shipped a fixed release or patch. You remain exposed.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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
An unspecified CGI script in Cisco FX-OS before 1.1.2 on Firepower 9000 devices and Cisco Unified Computing System (UCS) Manager before 2.2(4b), 2.2(5) before 2.2(5a), and 3.0 before 3.0(2e) allows remote attackers to execute arbitrary shell commands via a crafted HTTP request, aka Bug ID CSCur90888.

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
How this class of weakness works · CWE-78

User input reaches a shell or system command without being fully separated from the command itself, so an attacker can append their own instructions. Because these run with the application's privileges, it often means full control of the host. The lasting fix is to avoid the shell entirely — call APIs directly and pass arguments as data, never as concatenated strings.

General guidance for the os command injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Affected:= 1.1\(1.86\)= 1.1\(1.160\)= 1.1.1
Unified Computing SystemApplication
Affected:= 1.0\(2k\)= 1.0_base= 1.1\(1m\)= 1.1_base= 1.2\(1d\)= 1.2_base= 1.3\(1c\)= 1.3\(1m\)= 1.3\(1n\)= 1.3\(1o\)= 1.3\(1p\)= 1.3\(1q\)

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.

dbcve · scoped
Recommended fix High confidence

Cisco FX-OS 1.1.2+ for Firepower 9000; Cisco UCS Manager 2.2(4b), 2.2(5a), or 3.0(2e)+ depending on major version branch

  1. 1. Identify the current version of Cisco FX-OS (for Firepower 9000) or Cisco UCS Manager by logging into the device management interface
  2. 2. For Firepower 9000 devices running FX-OS: Plan upgrade to FX-OS version 1.1.2 or later
  3. 3. For Cisco UCS Manager: Determine if running version 2.2(4), 2.2(5), or 3.0(x) and plan upgrade to 2.2(4b), 2.2(5a), or 3.0(2e) respectively, or later
  4. 4. Review Cisco release notes for upgrade prerequisites and compatibility requirements
  5. 5. Schedule maintenance window as upgrades may require brief downtime
  6. 6. Perform backup of current configuration before upgrading
  7. 7. Download the appropriate firmware/software from Cisco.com (requires valid service contract)
  8. 8. Follow Cisco's documented upgrade procedure for your specific platform
Caveat Review Cisco release notes for potential compatibility issues; some upgrades may require intermediate steps if jumping multiple major versions

Generated from the published advisory — verify against the referenced sources before acting.

No vendor fix exists Firepower Extensible Operating System has not published a patch for this.

There is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.

Add your voice

Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.

Can’t wait

We develop and verify an original fix where the vendor hasn’t, from $3,550. Deployed to your staging first — never straight to production.

Scope it with us

See what else the community needs solved on the solutions-needed board.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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