Firesight System SoftwareApplication · Cisco

CVE-2015-0706

MEDIUM · 5.8 CVSS v2.0 Published 2015-04-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
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
Open redirect vulnerability in Cisco FireSIGHT System Software 5.3.1.1, 5.3.1.2, and 6.0.0 in FireSIGHT Management Center allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a crafted HTTP header, aka Bug IDs CSCut06060, CSCut06056, and CSCus98966.

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

Open redirect vulnerability in Cisco FireSIGHT Management Center allows remote attackers to redirect users to arbitrary external websites via crafted HTTP headers. The vulnerability affects versions 5.3.1.1, 5.3.1.2, and 6.0.0, enabling phishing attacks by manipulating the HTTP header to control the redirect destination.

MitigationApply the vendor-supplied software patch or upgrade to a fixed version of Cisco FireSIGHT System Software. Until patched, monitor for suspicious redirect patterns in HTTP headers targeting the Management Center interface.

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= 5.3.1.2= 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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
None

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

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 installed FireSIGHT System Software version
    Access the Management Center console or use the command line interface (CLI) with appropriate admin credentials and run the command to display the system version (typically via 'show version' or checking the web UI about page)
    Affected if The displayed version is exactly 5.3.1.1, 5.3.1.2, or 6.0.0
  2. Confirm Management Center web interface is accessible
    Attempt to reach the FireSIGHT Management Center login page via HTTP/HTTPS from a test system to verify the web interface is exposed
    Affected if The Management Center web interface responds to HTTP requests, making it reachable for potential exploit attempts
  3. Review HTTP traffic logs for redirect patterns
    Examine access logs, proxy logs, or IDS/IPS alerts for requests containing unusual redirect destinations or suspicious URL parameters targeting the Management Center
    Affected if Logs show requests with crafted HTTP headers or redirect parameters pointing to external domains not controlled by the organization
  4. Inspect configured redirect rules or URL handlers
    Check the Management Center configuration for any custom redirect rules, URL rewrite settings, or HTTP header handling configurations that could be manipulated
    Affected if Redirect rules exist that accept user-supplied input for destination URLs without proper validation

A user is affected if their Management Center runs version 5.3.1.1, 5.3.1.2, or 6.0.0 and has its web interface exposed to network traffic.

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 vendor-supplied software patch or upgrade to a fixed version of Cisco FireSIGHT System Software. Until patched, monitor for suspicious redirect patterns in HTTP headers targeting the Management Center interface.

Fix this in Firesight System Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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