Firesight System SoftwareApplication · Cisco

CVE-2015-0773

MEDIUM · 5.5 CVSS v2.0 Published 2015-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable 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
Cisco FireSIGHT System Software 5.3.1.3 and 6.0.0 allows remote authenticated users to delete an arbitrary user's dashboard via a modified VPN deletion request in a management session, aka Bug ID CSCut67078.

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 · moderate confidence

Cisco FireSIGHT System Software versions 5.3.1.3 and 6.0.0 contains an access control bypass where authenticated users can delete arbitrary user dashboards by modifying parameters in VPN deletion requests within management sessions. This is an Insecure Direct Object Reference (IDOR) vulnerability allowing unauthorized dashboard deletion across users.

MitigationApply Cisco's security update/patch for this vulnerability. If unavailable, restrict management interface access to trusted administrators only and implement audit logging for dashboard deletion operations.

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
Firesight System SoftwareApplication
Affected:= 5.3.1.1= 6.0.0

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
Authentication
Single
Confidentiality
None
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/C:N/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 installed Cisco FireSIGHT System Software version
    Log into the FireSIGHT management console and navigate to System > Updates > Product Updates, or run 'show version' via CLI on the management appliance
    Affected if The installed version is 5.3.1.1 or 6.0.0 exactly (these are the affected versions listed)
  2. Verify management interface accessibility
    Confirm whether the FireSIGHT management interface (HTTPS on port 443) is accessible from network segments outside the trusted admin network
    Affected if The management interface is exposed to untrusted networks, allowing remote authenticated attackers to exploit the IDOR vulnerability
  3. Confirm user authentication is enabled for management access
    Check that user authentication is required for accessing the FireSIGHT management console - verify in System > Users > Local User Management that local users are configured and authentication is enforced
    Affected if Authentication is enabled (which is required for the vulnerability to be exploitable - the flaw allows authenticated users to access other users' dashboards)
  4. Review user dashboard access logs for unauthorized deletions
    Examine the FireSIGHT management logs under System > Logs > Audit for events indicating dashboard deletions, particularly those performed by users deleting dashboards they do not own
    Affected if Audit logs show dashboard deletion events with mismatched user context (user A deleted user B's dashboard)

You are affected if your FireSIGHT management center runs version 5.3.1.1 or 6.0.0 AND the management interface is accessible to authenticated users who could exploit the IDOR flaw to delete arbitrary dashboards.

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 Cisco's security update/patch for this vulnerability. If unavailable, restrict management interface access to trusted administrators only and implement audit logging for dashboard deletion operations.

Fix this in Firesight System Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-0773 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