Adaptive Security Appliance SoftwareApplication · Cisco

CVE-2018-15388

HIGH · 8.6 CVSS v3.0 Published 2019-05-03
Fix available
A fix is available. Upgrade to 6.2.3.12 / 9.4.4.34 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 WebVPN login process of Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to cause increased CPU utilization on an affected device. The vulnerability is due to excessive processing load for existing WebVPN login operations. An attacker could exploit this vulnerability by sending multiple WebVPN login requests to the device. A successful exploit could allow the attacker to increase CPU load on the device, resulting in a denial of service (DoS) condition.

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 · moderate confidence

A denial of service vulnerability in Cisco ASA and FTD WebVPN login processing allows an unauthenticated remote attacker to send multiple login requests, causing excessive CPU load on the affected device due to inefficient processing of these requests.

MitigationApply the Cisco software update for CVE-2018-15388 when available, or implement rate limiting on WebVPN login endpoints and restrict WebVPN access to authorized IP ranges as a temporary workaround.

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
Adaptive Security Appliance SoftwareApplication
Affected:< 9.4.4.34>= 9.5, < 9.6.4.25>= 9.7, < 9.8.4>= 9.9, < 9.9.2.50
Secure Firewall Threat DefenseApplication
Affected:< 6.2.3.12

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.0/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. Verify if WebVPN is enabled on the device
    Run the command 'show webvpn' in ASA/FTD CLI or check the configuration with 'show running-config webvpn'
    Affected if WebVPN is enabled and configured - the vulnerability only affects devices with WebVPN feature active
  2. Check the installed ASA software version
    Run the command 'show version' in ASA CLI and look for the software version number in the output
    Affected if Version matches any of these ranges: < 9.4.4.34 OR >= 9.5 AND < 9.6.4.25 OR >= 9.7 AND < 9.8.4 OR >= 9.9 AND < 9.9.2.50
  3. Check the installed FTD software version
    Run 'show version' in FTD CLI or access the FTD management console to view the software version
    Affected if Version is lower than 6.2.3.12
  4. Check for high CPU usage from WebVPN processes
    Run 'show processes cpu history' and look for elevated CPU usage; use 'show processes' to identify WebVPN-related processes consuming excessive CPU
    Affected if WebVPN or sslvpnd processes are consuming unusually high CPU, especially during login attempts

A user is affected if WebVPN is enabled and the installed ASA or FTD version falls within any of the vulnerable version ranges listed.

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 6.2.3.12 / 9.4.4.34 / 9.6.4.25 or later
Fixed in 6.2.3.129.4.4.349.6.4.25
Interim mitigation

Apply the Cisco software update for CVE-2018-15388 when available, or implement rate limiting on WebVPN login endpoints and restrict WebVPN access to authorized IP ranges as a temporary workaround.

Fix this in Adaptive Security Appliance Software 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 the upgrade done

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