dbcve.org
Email Security ApplianceApplication · Cisco

CVE-2016-6360

HIGH · 7.5 CVSS v3.0 Published 2016-10-28
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
A vulnerability in Advanced Malware Protection (AMP) for Cisco Email Security Appliances (ESA) and Web Security Appliances (WSA) could allow an unauthenticated, remote attacker to cause a partial denial of service (DoS) condition due to the AMP process unexpectedly restarting. Affected Products: Cisco AsyncOS Software for Email Security Appliances (ESA) versions 9.5 and later up to the first fixed release, Cisco AsyncOS Software for Web Security Appliances (WSA) all versions prior to the first fixed release. More Information: CSCux56406, CSCux59928. Known Affected Releases: 9.6.0-051 9.7.0-125 8.8.0-085 9.5.0-444 WSA10.0.0-000. Known Fixed Releases: 9.7.1-066 WSA10.0.0-233.

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 vulnerability in Cisco Advanced Malware Protection (AMP) for Email Security Appliances (ESA) and Web Security Appliances (WSA) allows an unauthenticated, remote attacker to cause a partial denial of service by triggering an unexpected restart of the AMP process. The issue affects AsyncOS software versions 9.5 and later for ESA, and all versions prior to the fixed release for WSA.

MitigationApply the vendor-supplied fixed software releases (ESA: 9.7.1-066 or later; WSA: 10.0.0-233 or later) after scheduling a maintenance window and testing in a non-production environment.

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
Email Security ApplianceApplication
Affected:= 9.5.0-000= 9.5.0-201= 9.6.0-000= 9.6.0-042= 9.6.0-051= 9.7.0-125
Web Security ApplianceApplication
Affected:= 8.8.0-085= 9.0.0-193= 9.0_base= 9.1.0-000= 9.1.0-070= 9.1_base= 9.5.0-235= 9.5.0-284= 9.5.0-444= 9.5_base

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 the Cisco appliance product type
    Log into the device CLI or web interface and confirm whether it is an Email Security Appliance (ESA) or Web Security Appliance (WSA). This determines which version range applies.
    Affected if The device is an ESA or WSA model.
  2. Determine the installed AsyncOS version on ESA
    In the ESA CLI, run the command 'version' or access the web interface under System Administration > Software Updates to view the AsyncOS version. Compare the version number to the affected ESA range: 9.5.0-000 through 9.7.0-125.
    Affected if The ESA runs AsyncOS version 9.5.x or 9.6.x, or version 9.7.0-125.
  3. Determine the installed AsyncOS version on WSA
    In the WSA CLI, run the command 'version' or access the web interface under System Administration > System Upgrade to view the AsyncOS version. Compare the version number to the affected WSA range: 8.8.0-085, 9.0.x, 9.1.x, and 9.5.x versions prior to 10.0.0-233.
    Affected if The WSA runs any AsyncOS version from 8.8.x, 9.0.x, 9.1.x, or 9.5.x.
  4. Verify if AMP is enabled on the appliance
    On ESA, check via the web interface under Security Services > IronPort Anti-Malware or via CLI command 'ampconfig'. On WSA, check under Security Services > Anti-Malware. The vulnerability affects the AMP process specifically.
    Affected if AMP is enabled and running on the device.

A user is affected if they run an ESA with AsyncOS 9.5.x through 9.7.0-125 or a WSA with AsyncOS 8.8.x through 9.5.x, and have AMP enabled.

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 fixed software releases (ESA: 9.7.1-066 or later; WSA: 10.0.0-233 or later) after scheduling a maintenance window and testing in a non-production environment.

Fix this in Email Security Appliance Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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