CVE-2021-40125
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 · uneditedA vulnerability in the Internet Key Exchange Version 2 (IKEv2) implementation of Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an authenticated, remote attacker to trigger a denial of service (DoS) condition on an affected device. This vulnerability is due to improper control of a resource. An attacker with the ability to spoof a trusted IKEv2 site-to-site VPN peer and in possession of valid IKEv2 credentials for that peer could exploit this vulnerability by sending malformed, authenticated IKEv2 messages to an affected device. A successful exploit could allow the attacker to trigger a reload of the 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 · moderate confidenceA resource management vulnerability in Cisco ASA and FTD software's IKEv2 implementation allows an authenticated attacker who can spoof a trusted VPN peer and possesses valid IKEv2 credentials to send malformed IKEv2 messages, triggering a device reload and denial of service.
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< 6.4.0.13>= 6.6.0, < 6.6.5>= 6.7.0, < 6.7.0.3>= 7.0.0, < 7.0.1>= 9.8.0, < 9.8.4.40>= 9.9.0, < 9.12.4.30>= 9.14.0, < 9.14.3.9>= 9.15.0, < 9.15.1.17>= 9.16.0, < 9.16.2= 009.016\(001.025\)= 009.016\(001.025\)= 009.016\(001.025\)= 009.016\(001.025\)= 009.016\(001.025\)= 009.016\(001.025\)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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify product type and versionRun 'show version' on the device CLI to determine if running Cisco ASA Software or Firepower Threat Defense (FTD) and note the exact version numberAffected if The device runs Cisco ASA Software or FTD and the version falls within the affected ranges listed in the CVE advisory
-
Verify IKEv2 is enabledRun 'show crypto ikev2' or 'show run crypto ikev2' to check if IKEv2 protocol is configured on the deviceAffected if IKEv2 is actively configured or enabled on the device
-
Check for IKEv2 VPN configurationsRun 'show crypto ipsec sa' or 'show run tunnel-group' to identify any IKEv2 VPN tunnels that are definedAffected if Any IKEv2 VPN tunnels or remote access/site-to-site configurations using IKEv2 are present
-
Compare installed version to affected rangesCompare your exact version from step 1 against the affected version ranges: FTD < 6.4.0.13, 6.6.0 to < 6.6.5, 7.0.0 to < 7.0.1; ASA 9.8.0 to < 9.8.4.40, 9.9.0 to < 9.12.4.30, 9.14.0 to < 9.14.3.9, 9.15.0 to < 9.15.1.17, 9.16.0 to < 9.16.2; or specific firmware 009.016(001.025) for ASA 5505/5512X/5515X/5525X/5545X/5555XAffected if The installed version matches one of the affected version ranges
Device is affected if it runs a vulnerable ASA or FTD version within the listed ranges AND has IKEv2 protocol enabled or configured for VPN connections.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped6.4.0.136.6.56.7.0.3
Apply the Cisco security updates for ASA and FTD software. Ensure IKEv2 credentials are properly secured and monitor for anomalous IKEv2 traffic patterns that may indicate credential compromise or spoofing attempts.
Minimum fixed versions: FTD 6.4.0.13, 6.6.5, 6.7.0.3, 7.0.1 | ASA 9.8.4.40, 9.12.4.30, 9.14.3.9, 9.15.1.17 (choose based on current branch)
- 1. Identify the current version of Cisco ASA Software or Firepower Threat Defense (FTD) by running 'show version' on the device
- 2. Based on the current version branch, determine the minimum fixed release from the Cisco advisory: For FTD 6.4.x, upgrade to 6.4.0.13 or later; For FTD 6.6.x, upgrade to 6.6.5 or later; For FTD 6.7.x, upgrade to 6.7.0.3 or later; For FTD 7.0.x, upgrade to 7.0.1 or later; For ASA 9.8.x, upgrade to 9.8.4.40 or later; For ASA 9.9.x-9.12.x, upgrade to 9.12.4.30 or later; For ASA 9.14.x, upgrade to 9
- 3. Download the appropriate fixed software image from Cisco (requires valid CCO account)
- 4. Upload the new software image to the device using 'copy' command or through the device management interface
- 5. Install the upgrade using the 'install' command (for FTD) or reload the device after the software upgrade (for ASA)
- 6. Verify the new version is running with 'show version' and confirm the IKEv2 vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-40125 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-40125 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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