Anyconnect Secure Mobility ClientApplication · Cisco

CVE-2021-1496

HIGH · 7.8 CVSS v3.1 Published 2021-05-06
Fix available
A fix is available. Upgrade to 4.9.03022 or later.
See remediation →
80/100
Remediation priority · High
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
Multiple vulnerabilities in the install, uninstall, and upgrade processes of Cisco AnyConnect Secure Mobility Client for Windows could allow an authenticated, local attacker to hijack DLL or executable files that are used by the application. A successful exploit could allow the attacker to execute arbitrary code on an affected device with SYSTEM privileges. To exploit these vulnerabilities, the attacker must have valid credentials on the Windows system. For more information about these vulnerabilities, see the Details section of this advisory.

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

Multiple vulnerabilities in Cisco AnyConnect Secure Mobility Client for Windows allow DLL and executable hijacking during install, uninstall, and upgrade processes. An authenticated local attacker can hijack files to execute arbitrary code with SYSTEM privileges.

MitigationApply Cisco's vendor patches for AnyConnect Secure Mobility Client. Ensure strict file permissions on application directories and restrict local user access to prevent exploitation.

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.03022

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Check if Cisco AnyConnect is installed
    Inspect the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for any entry with 'Cisco AnyConnect' in the DisplayName field, or look for the program directory in C:\Program Files\Cisco\Cisco AnyConnect Secure Mobility Client
    Affected if AnyConnect Secure Mobility Client is found on the system
  2. Determine the installed version number
    Read the Version value from the same registry key where the Cisco AnyConnect entry was found, or locate the client.exe file in the install directory and view its file properties
    Affected if The discovered version is a numeric value less than 4.9.03022
  3. Compare version against the fixed release
    Compare the identified version string numerically against 4.9.03022, noting that any version below this threshold is affected
    Affected if The installed version is below 4.9.03022 (for example, 4.8.02042 or 4.7.01036)
  4. Identify the installation directory
    Locate the directory where AnyConnect is installed, typically found in the InstallLocation registry value or under C:\Program Files\Cisco\Cisco AnyConnect Secure Mobility Client
    Affected if The software is installed in a directory accessible to authenticated local users

The system is affected if Cisco AnyConnect Secure Mobility Client is installed with a version lower than 4.9.03022.

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 4.9.03022 or later
Fixed in 4.9.03022
Interim mitigation

Apply Cisco's vendor patches for AnyConnect Secure Mobility Client. Ensure strict file permissions on application directories and restrict local user access to prevent exploitation.

Fix this in Anyconnect Secure Mobility Client 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-2021-1496 — 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-2021-1496 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