Secure Firewall Threat DefenseApplication · Cisco
CVE-2019-1708
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 Mobility and Multihoming Protocol (MOBIKE) feature for the Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to cause a memory leak or a reload of an affected device that leads to a denial of service (DoS) condition. The vulnerability is due to the incorrect processing of certain MOBIKE packets. An attacker could exploit this vulnerability by sending crafted MOBIKE packets to an affected device to be processed. A successful exploit could cause an affected device to continuously consume memory and eventually reload, resulting in a DoS condition. The MOBIKE feature is supported only for IPv4 addresses.
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 confidenceA memory corruption vulnerability exists in the MOBIKE (IKEv2 Mobility and Multihoming) feature of Cisco ASA and FTD software. The flaw is in the incorrect processing of specially crafted MOBIKE packets, which causes the affected device to continuously leak memory with each processed packet. An unauthenticated remote attacker can send malicious MOBIKE packets to exhaust device memory, forcing a reload and resulting in denial of service. The vulnerability affects only IPv4 MOBIKE configurations.
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
Secure Firewall Threat DefenseApplication
>= 6.2.2, <= 6.2.3.12>= 6.3.0, <= 6.3.0.3
Adaptive Security Appliance SoftwareOperating system
>= 9.8, <= 9.8.4>= 9.9, <= 9.9.2.50>= 9.10, <= 9.10.1.17CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Cisco device type and software versionExecute 'show version' on the device CLI to retrieve the installed ASA or FTD software version numberAffected if The device runs ASA software version 9.8.x through 9.10.1.17, or FTD software version 6.2.2 through 6.2.3.12, or 6.3.0 through 6.3.0.3
-
Determine if MOBIKE is enabled on IKEv2 VPN tunnelsExamine the IKEv2 VPN configuration using 'show running-config crypto ikev2' or review tunnel group settings for MOBIKE-related commands such as 'mobike enable'Affected if MOBIKE is explicitly enabled on any IKEv2 tunnel configuration on the device
-
Confirm IPv4 is used for MOBIKE-enabled tunnelsReview the IP addressing configuration for the VPN tunnel interfaces where MOBIKE is enabled; check if IPv4 addresses are assigned using 'show ip address' or interface configurationAffected if MOBIKE is enabled and the device processes IPv4 traffic (the vulnerability only affects IPv4 MOBIKE configurations)
-
Check for memory exhaustion symptomsMonitor device memory with 'show memory' or 'show processes memory' to identify abnormal memory consumption patterns; look for steadily decreasing available memoryAffected if Device memory progressively decreases without recovery, indicating potential memory leak from processed MOBIKE packets
The device is affected if it runs a vulnerable ASA/FTD version AND has MOBIKE enabled on any IKEv2 tunnel carrying IPv4 traffic.
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.
From vendor dataApply the Cisco patch for CVE-2019-1708 to affected ASA/FTD software versions. If MOBIKE is not required, disable the MOBIKE feature as a defensive measure until patching can be completed.
Fix this in Secure Firewall Threat Defense
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2019-1708 — 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-2019-1708 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