dbcve.org
Firepower Extensible Operating SystemOperating system · Cisco

CVE-2015-6373

MEDIUM · 6.8 CVSS v2.0 Published 2015-11-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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
Cross-site request forgery (CSRF) vulnerability in Cisco Firepower Extensible Operating System 1.1(1.160) on Firepower 9000 devices allows remote attackers to hijack the authentication of arbitrary users, aka Bug ID CSCux10611.

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

Cross-site request forgery (CSRF) vulnerability in Cisco Firepower Extensible Operating System 1.1(1.160) on Firepower 9000 devices allows remote attackers to hijack the authentication of arbitrary users by tricking authenticated users into submitting malicious requests.

MitigationApply the Cisco firmware update for Firepower 9000 devices addressing CSCux10611, and implement anti-CSRF tokens and proper referrer validation in web application interfaces.

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
Affected:= 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
Network
Complexity
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

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 Firepower device model
    Access the device CLI or web interface and retrieve the hardware model information. For CLI, use 'show version' or 'show inventory' commands. Look for Firepower 9000 series identifiers.
    Affected if The device is NOT a Firepower 9000 series appliance (the vulnerability only affects Firepower 9000 devices).
  2. Check the Firepower Extensible Operating System version
    From the CLI, run 'show version' or 'show system software' to display the installed OS version. Alternatively, log into the web interface and navigate to System > Updates or About to view the firmware version.
    Affected if The installed version is exactly 1.1(1.160) - no other versions are listed as affected for this specific CVE.
  3. Verify the web management interface is accessible
    Confirm the device has the web-based GUI enabled and accessible. Check if HTTP/HTTPS ports for the Firepower management interface are listening and reachable on the network.
    Affected if The web interface is enabled and reachable - the CSRF vulnerability exploits the web interface, so if no web interface exists, the attack surface is not present.
  4. Confirm authentication is required for web interface access
    Verify that the Firepower web management interface requires authentication. Attempt to access the interface or check configuration for authentication settings.
    Affected if The web interface allows authenticated sessions - the vulnerability hijacks existing authenticated user sessions, so unauthenticated interfaces are not affected by this specific CSRF flaw.

You are affected only if you have a Firepower 9000 device running exactly version 1.1(1.160) of the Firepower Extensible Operating System with its web management interface enabled and accessible.

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 firmware update for Firepower 9000 devices addressing CSCux10611, and implement anti-CSRF tokens and proper referrer validation in web application interfaces.

Fix this in Firepower Extensible Operating System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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