dbcve.org
Anyconnect Secure Mobility ClientApplication · Cisco

CVE-2024-20474

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Internet Key Exchange version 2 (IKEv2) processing of Cisco Secure Client Software could allow an unauthenticated, remote attacker to cause a denial of service (DoS) of Cisco Secure Client. This vulnerability is due to an integer underflow condition. An attacker could exploit this vulnerability by sending a crafted IKEv2 packet to an affected system. A successful exploit could allow the attacker to cause Cisco Secure Client Software to crash, resulting in a DoS condition on the client software. Note: Cisco Secure Client Software releases 4.10 and earlier were known as Cisco AnyConnect Secure Mobility Client.

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

This is an integer underflow vulnerability in IKEv2 packet processing within Cisco Secure Client (formerly Cisco AnyConnect). An unauthenticated remote attacker can send a specially crafted IKEv2 packet to trigger the underflow, causing the client software to crash and result in a denial of service condition.

MitigationApply the vendor patch for Cisco Secure Client when released. Until then, limit exposure by avoiding untrusted VPN connections and monitoring for client crashes.

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
Anyconnect Secure Mobility ClientApplication
Affected:= 4.9.00086= 4.9.01095= 4.9.02028= 4.9.03047= 4.9.03049= 4.9.04043= 4.9.04053= 4.9.05042= 4.9.06037
Secure ClientApplication
Affected:= 4.10.00093= 4.10.01075= 4.10.02086= 4.10.03104= 4.10.04065= 4.10.04071= 4.10.05085= 4.10.05095= 4.10.05111= 4.10.06079= 4.10.06090= 4.10.07061

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
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Cisco VPN client version
    Open Windows Control Panel > Programs and Features, look for 'Cisco AnyConnect Secure Mobility Client' or 'Cisco Secure Client' and note the version number. Alternatively, run 'vpncli.exe -v' or 'vpn --version' from the client installation directory.
    Affected if The installed version matches any of these: 4.9.00086, 4.9.01095, 4.9.02028, 4.9.03047, 4.9.03049, 4.9.04043, 4.9.04053, 4.9.05042, 4.9.06037, 4.10.00093, 4.10.01075, 4.10.02086, 4.10.03104, 4.10.04065, 4.10.04071, 4.10.05085, 4.10.05095, 4.10.05111, 4.10.06079, 4.10.06090, 4.10.07061
  2. Verify IKEv2 VPN profile is configured
    Check the client's profile XML files in the profile directory (typically C:\ProgramData\Cisco\Cisco Secure Client\profiles\ or within the client UI under Profile Management). Look for a profile with <Protocol>IKEv2</Protocol> or similar IKEv2 configuration.
    Affected if An IKEv2 VPN profile exists and is available for connection, as the vulnerability is triggered during IKEv2 packet processing.
  3. Confirm client is running or configured for auto-connect
    Check if the Cisco client service (Cisco AnyConnect Service or Cisco Secure Client Service) is running, or if the client is set to auto-connect on system startup.
    Affected if The client is active and capable of receiving IKEv2 packets from a VPN server, making it reachable for exploitation.

You are affected if your installed Cisco AnyConnect Secure Mobility Client or Cisco Secure Client version matches one of the listed versions AND you have an IKEv2 VPN profile configured, as the integer underflow triggers when processing a specially crafted IKEv2 packet.

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 patch for Cisco Secure Client when released. Until then, limit exposure by avoiding untrusted VPN connections and monitoring for client crashes.

Fix this in Anyconnect Secure Mobility Client Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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