dbcve.org
Web Security ApplianceApplication · Cisco

CVE-2016-1380

HIGH · 7.5 CVSS v3.0 Published 2016-05-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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.0 before 8.0.6-119 on Web Security Appliance (WSA) devices allows remote attackers to cause a denial of service (proxy-process hang) via a crafted HTTP POST request, aka Bug ID CSCuo12171.

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

A denial of service vulnerability exists in Cisco AsyncOS 8.0 before version 8.0.6-119 on Web Security Appliance (WSA) devices. Remote attackers can cause the proxy-process to hang by sending a crafted HTTP POST request.

MitigationApply the vendor patch by upgrading Cisco AsyncOS to version 8.0.6-119 or later.

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.6-119= 8.0.7= 8.0.7-142= 8.0.8-mr-113= 8.5.0-000= 8.5.0-497= 8.5.1-021= 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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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 AsyncOS version
    Access the WSA CLI and run the command 'version' or use the web GUI under System Administration > Software Updates to view the current AsyncOS version
    Affected if The installed version is 8.0.0-000, 8.0.5, 8.0.6, 8.0.6-078, 8.0.7, 8.0.7-142, 8.0.8-mr-113, 8.5.0-000, 8.5.0-497, 8.5.1-021, or 8.5.2-024 (all versions before 8.0.6-119)
  2. Confirm WSA web proxy is enabled
    Log into the WSA web GUI and navigate to Security Services > Web Proxy, or use the CLI command 'proxy config'
    Affected if The web proxy service is enabled (the vulnerability requires the proxy to be active to accept the malicious HTTP POST request)
  3. Verify proxy process responsiveness
    Use the CLI command 'proxy status' or monitor the WSA dashboard for proxy process health indicators
    Affected if The proxy process shows as hung, unresponsive, or experiencing unusual restarts

A user is affected if their WSA runs any AsyncOS version before 8.0.6-119 AND has the web proxy service enabled, making it susceptible to the crafted HTTP POST request denial of service.

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 patch by upgrading Cisco AsyncOS to version 8.0.6-119 or later.

Fix this in Web Security Appliance Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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 locally
dbcve dependency scanner

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