AsyncosOperating system · Cisco

CVE-2018-15460

HIGH · 8.6 CVSS v3.1 Published 2019-01-10
Fix available
A fix is available. Upgrade to 11.0.2-044_md / 11.1.2-023_md or later.
See remediation →
95/100
Remediation priority · Urgent
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 the email message filtering feature of Cisco AsyncOS Software for Cisco Email Security Appliances (ESA) could allow an unauthenticated, remote attacker to cause the CPU utilization to increase to 100 percent, causing a denial of service (DoS) condition on an affected device. The vulnerability is due to improper filtering of email messages that contain references to whitelisted URLs. An attacker could exploit this vulnerability by sending a malicious email message that contains a large number of whitelisted URLs. A successful exploit could allow the attacker to cause a sustained DoS condition that could force the affected device to stop scanning and forwarding email messages.

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 Email Security Appliance contains a DoS vulnerability in the URL filtering logic. When processing email messages containing excessive references to whitelisted URLs, the device's CPU utilization spikes to 100% and remains there, halting all email scanning and forwarding capabilities. The vulnerability is exploitable remotely by unauthenticated attackers sending specially crafted emails.

MitigationApply Cisco's available software update for CVE-2018-15460. As an interim measure, consider disabling URL filtering or implementing rate limiting on the ESA while awaiting the patch.

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
AsyncosOperating system
Affected:< 11.0.2-044_md>= 11.1.0, < 11.1.2-023_md

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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
    Log into the ESA CLI and run the 'version' command, or check via the web interface under System Administration > Upgrade
    Affected if Version is below 11.0.2-044_md, OR version is 11.1.0 through 11.1.2-023_md
  2. Verify URL filtering is enabled
    Log into the ESA web interface and navigate to Security Services > URL Filtering to confirm the feature is turned on
    Affected if URL filtering is enabled AND the AsyncOS version falls within the vulnerable version ranges
  3. Monitor CPU utilization
    Check the ESA web interface Dashboard or use the CLI command 'status' to view current CPU usage
    Affected if CPU utilization is at or near 100% and email processing has halted
  4. Check mail queue status
    Use the ESA CLI command 'mailq' or view the Message Tracking in the web interface to see if messages are stuck
    Affected if Email messages are queued and not being processed, with the ESA appearing unresponsive

Your ESA is affected if it runs a vulnerable AsyncOS version AND has URL filtering enabled, particularly if you observe sustained high CPU usage and halted mail processing.

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
Upgrade available Upgrade to 11.0.2-044_md / 11.1.2-023_md or later
Fixed in 11.0.2-044_md11.1.2-023_md
Interim mitigation

Apply Cisco's available software update for CVE-2018-15460. As an interim measure, consider disabling URL filtering or implementing rate limiting on the ESA while awaiting the patch.

Fix this in Asyncos 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 the upgrade done

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-2018-15460 — 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-2018-15460 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