Web Security ApplianceApplication · Cisco
CVE-2015-6292
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 · uneditedThe proxy-cache implementation in Cisco AsyncOS 8.0.x before 8.0.7-151, 8.1.x and 8.5.x before 8.5.2-004, 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 proxy connections, aka Bug ID CSCus10922.
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 confidenceMemory exhaustion DoS in Cisco Web Security Appliance (WSA) proxy-cache. Remote attackers can cause memory consumption by opening multiple proxy connections, potentially crashing the proxy service.
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
= 8.0.0-000= 8.0.5= 8.0.6= 8.0.6-119= 8.5.0-497= 8.5.0.000CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device as Cisco Web Security ApplianceLog into the WSA administrative interface or use the CLI command 'version' to confirm the device model is Cisco Web Security ApplianceAffected if The device is not a Cisco WSA (this CVE does not apply)
-
Check installed firmware versionRun 'version' in the WSA CLI or view the version in the web interface under System Administration > System UpgradeAffected if The installed version matches 8.0.0-000, 8.0.5, 8.0.6, 8.0.6-119, 8.5.0-497, or 8.5.0-000
-
Verify the proxy service is enabledIn the WSA web interface, navigate to Security Services > Proxy Settings or use CLI command 'proxy config' to confirm the proxy feature is turned onAffected if The proxy service is enabled and the version matches affected versions from step 2
-
Check proxy access controlsIn the WSA web interface, go to Security Services > Proxy Access Settings and review the ACLs or destination groups that control which clients can connect to the proxyAffected if The proxy allows connections from untrusted or external networks without proper restrictions
You are affected if you are running a Cisco WSA with firmware version 8.0.0-000, 8.0.5, 8.0.6, 8.0.6-119, 8.5.0-497, or 8.5.0-000 and the proxy service is enabled and accessible to untrusted sources.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Cisco firmware updates for affected versions (8.0.7-151, 8.5.2-004, 8.7.0-171-LD, 8.8.0-085 or later). If immediate patching is not possible, consider rate-limiting proxy connections or restricting proxy access to trusted sources via ACLs.
Fix this in Web Security Appliance
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6292 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-6292 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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