dbcve.org
Adaptive Security Appliance SoftwareOperating system · Cisco

CVE-2025-20182

HIGH · 8.6 CVSS v3.1 Published 2025-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Internet Key Exchange version 2 (IKEv2) protocol processing of Cisco Adaptive Security Appliance (ASA) Software, Cisco Firepower Threat Defense (FTD) Software, Cisco IOS Software, and Cisco IOS XE Software could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. This vulnerability is due to insufficient input validation when processing IKEv2 messages. An attacker could exploit this vulnerability by sending crafted IKEv2 traffic to an affected device. A successful exploit could allow the attacker to cause the device to reload, resulting in a DoS condition on the affected device.

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 the IKEv2 protocol processing of Cisco ASA, FTD, IOS, and IOS XE Software allows an unauthenticated remote attacker to send crafted IKEv2 messages that exploit insufficient input validation, causing the affected device to reload and result in a denial of service condition.

MitigationApply the vendor-supplied security updates/patches for this vulnerability. If patches are unavailable, consider blocking IKEv2 traffic at network perimeter or disabling IKEv2 on affected interfaces if not required.

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 SoftwareOperating system
Affected:= 9.8.1= 9.8.1.5= 9.8.1.7= 9.8.2= 9.8.2.8= 9.8.2.14= 9.8.2.15= 9.8.2.17= 9.8.2.20= 9.8.2.24= 9.8.2.26= 9.8.2.28
Secure Firewall Threat DefenseApplication
Affected:= 6.2.3= 6.2.3.1= 6.2.3.2= 6.2.3.3= 6.2.3.4= 6.2.3.5= 6.2.3.6= 6.2.3.7= 6.2.3.8= 6.2.3.9= 6.2.3.10= 6.2.3.11

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 Cisco product and software version
    Run 'show version' on the device CLI to determine if it is running ASA, FTD, IOS, or IOS XE Software, and record the exact software version number displayed.
    Affected if The device runs ASA, FTD, IOS, or IOS XE Software and the version matches one of the listed affected versions.
  2. Verify IKEv2 is configured
    Run 'show crypto ikev2 sa' or 'show running-config | include ikev2' to check if IKEv2 is enabled on any interface. Also check crypto maps and tunnel groups with 'show run | grep -i ikev2'.
    Affected if IKEv2 is actively configured or enabled on the device, making the IKEv2 processing code path reachable.
  3. Check for active IKEv2 tunnels
    Run 'show crypto ikev2 session' to view active IKEv2 sessions. Run 'show crypto ipsec sa' to see established IPsec tunnels that may use IKEv2.
    Affected if There are active IKEv2 tunnels or the device is negotiating IKEv2 with remote peers.
  4. Compare version against affected list
    For ASA: compare your version to 9.8.1, 9.8.1.5, 9.8.1.7, 9.8.2, 9.8.2.8, 9.8.2.14, 9.8.2.15, 9.8.2.17, 9.8.2.20, 9.8.2.24, 9.8.2.26, 9.8.2.28. For FTD: compare to 6.2.3 through 6.2.3.11 range. For IOS/IOS XE: contact Cisco or check security advisories for version-specific details.
    Affected if The running software version exactly matches one of the listed versions for ASA or FTD, or falls within the affected range for IOS/IOS XE.

The device is affected if it runs ASA or FTD Software matching exactly one of the listed versions (or IOS/IOS XE per Cisco advisory) AND has IKEv2 enabled or actively negotiating, because the crafted IKEv2 packet processing vulnerability will trigger a reload.

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 security updates/patches for this vulnerability. If patches are unavailable, consider blocking IKEv2 traffic at network perimeter or disabling IKEv2 on affected interfaces if not required.

Fix this in Adaptive Security Appliance Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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