dbcve.org
Web Security ApplianceApplication · Cisco

CVE-2015-6293

HIGH · 7.8 CVSS v2.0 Published 2015-11-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/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
Cisco AsyncOS 8.x before 8.0.8-113, 8.1.x and 8.5.x before 8.5.3-051, 8.6.x and 8.7.x before 8.7.0-171-LD, and 8.8.x before 8.8.0-085 on Web Security Appliance (WSA) devices allows remote attackers to cause a denial of service (memory consumption) via multiple file-range requests, aka Bug ID CSCur39155.

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

Cisco AsyncOS Web Security Appliance (WSA) versions 8.x before 8.0.8-113, 8.5.x before 8.5.3-051, 8.6.x and 8.7.x before 8.7.0-171-LD, and 8.8.x before 8.8.0-085 contain a denial of service vulnerability where multiple HTTP file-range requests cause excessive memory consumption, potentially rendering the device unresponsive.

MitigationUpgrade Cisco AsyncOS on WSA devices to the specified patched versions (8.0.8-113, 8.5.3-051, 8.7.0-171-LD, or 8.8.0-085 or later) to remediate the vulnerability.

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
Web Security ApplianceApplication
Affected:= 8.0.0-000= 8.0.5= 8.0.6= 8.0.6-078= 8.0.7-142= 8.0.8-mr-113= 8.5.0-497= 8.5.0.000= 8.5.2-024

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
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:L/Au:N/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Cisco WSA AsyncOS version via CLI
    Log into the WSA CLI and run the command: `version`. This displays the installed AsyncOS version and build number.
    Affected if The displayed version falls within these ranges: 8.0.x before 8.0.8-113, 8.5.x before 8.5.3-051, 8.6.x/8.7.x before 8.7.0-171-LD, or 8.8.x before 8.8.0-085.
  2. Verify version via web UI
    Access the WSA web interface, navigate to System Administration > Status and look for the AsyncOS version and build string.
    Affected if The version shown matches the affected ranges listed above.
  3. Confirm WSA is processing HTTP traffic
    The vulnerability is triggered by HTTP file-range requests sent through the appliance. Check if the WSA is deployed in a mode where it processes HTTP traffic (proxy mode, transparent proxy, or upstream proxy).
    Affected if The WSA is actively processing HTTP requests from clients. The vulnerability requires the device to be handling HTTP traffic to be exploitable.

A Cisco WSA is affected if it runs any AsyncOS version before 8.0.8-113, 8.5.3-051, 8.7.0-171-LD, or 8.8.0-085 and is processing HTTP 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

Upgrade Cisco AsyncOS on WSA devices to the specified patched versions (8.0.8-113, 8.5.3-051, 8.7.0-171-LD, or 8.8.0-085 or later) to remediate the vulnerability.

Fix this in Web Security Appliance 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-6293 — 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-6293 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