⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 7.8 ⚠ ACTIVELY EXPLOITED — CISA KEV

How to Fix CVE-2020-3433: Security Vulnerability in Cisco Anyconnect Secure Mobility Client

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 7.8 - High
Actively exploited?Yes, listed in CISA KEV (added 2022-10-24)
AffectedCisco AnyConnect Secure Mobility Client: n/a
Fixed inSee vendor advisory for the patched build
Type (CWE)CWE-427
Patch immediately. CISA's Known Exploited Vulnerabilities catalog lists this CVE, which means active exploitation has been confirmed. CISA KEV entry added 2022-10-24, federal due date 2022-11-14.

What is CVE-2020-3433?

CVE-2020-3433 is a security vulnerability in Cisco Anyconnect Secure Mobility Client from Cisco. A vulnerability in the interprocess communication (IPC) channel of Cisco AnyConnect Secure Mobility Client for Windows could allow an authenticated, local attacker to perform a DLL hijacking attack. To exploit this vulnerability, the attacker would need to have valid credentials on the Windows system. The vulnerability is due to insufficient validation of resources that are loaded by the application at run time.

Why this CVE matters

This CVE sits on CISA's Known Exploited Vulnerabilities catalog, which only happens after active exploitation is observed in the wild. The security vulnerability class of flaw gives attackers a reliable foothold against vulnerable instances of Cisco Anyconnect Secure Mobility Client. If your deployment matches the affected versions, treat any window of unpatched exposure as compromise-likely and review logs accordingly.

Am I affected?

Run the version check that matches your platform. If the installed build sits inside the affected range from the table above, the fix applies to you.


# Linux package check
dpkg -s ciscoanyconnectsecuremobilityclient 2>/dev/null | grep -i version    # Debian / Ubuntu
rpm -q ciscoanyconnectsecuremobilityclient 2>/dev/null                       # RHEL / Rocky


# Windows version check
Get-CimInstance Win32_Product | Where-Object { $_.Name -match 'Cisco Anyconnect Secure Mobility Client' } | Select-Object Name,Version


# Network appliance CLI
show version    # then compare against the 'Affected' row above

How to fix CVE-2020-3433

Apply the patched build the vendor names in the advisory. The commands below are starting points keyed to common platforms - adapt the package name and target version to your environment.

Cisco IOS / IOS XE CLI


# 1. Confirm the running image
show version | include Cisco IOS
show version | include System image

# 2. Copy the patched image you downloaded from Cisco's Software Center
# (always verify the SHA512 against cisco.com before installing)
copy tftp://10.0.0.10/Cisco AnyConnect Secure Mobility Client-patched.bin flash:

# 3. Set boot variable and reload
configure terminal
no boot system
boot system flash:Cisco AnyConnect Secure Mobility Client-patched.bin
end
write memory
reload

# 4. After the box comes back up
show version | include System image    # confirm patched filename

Windows (PowerShell, run as administrator)


# Vendor advisory: https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-anyconnect-dll-F26WwJW
# Make sure Windows Update is current. For monthly rollups this is the safest path.
Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -Confirm:$false
Import-Module PSWindowsUpdate
Get-WindowsUpdate -KBArticleID <KB-from-advisory>
Install-WindowsUpdate -KBArticleID <KB-from-advisory> -AcceptAll -AutoReboot

# Confirm the KB landed
Get-HotFix | Where-Object { $_.HotFixID -eq 'KB<id>' }

# Or, for an MSU file downloaded from the Microsoft Update Catalog:
wusa.exe C:\Patches\windows10.0-kb<id>-x64.msu /quiet /norestart
shutdown /r /t 60

PowerShell detect/upgrade/verify/log (Windows)


# CVE-2020-3433 remediation runner — adapt the version checks to your environment.
$log = "C:\Logs\CVE-2020-3433-fix.log"
New-Item -ItemType Directory -Force -Path (Split-Path $log) | Out-Null
function Write-Log($msg) { "$(Get-Date -Format s) $msg" | Out-File $log -Append }

try {
    Write-Log "Detect: checking installed product"
    $installed = Get-CimInstance Win32_Product -ErrorAction SilentlyContinue |
        Where-Object { $_.Name -match 'Cisco AnyConnect Secure Mobility Client' }
    if (-not $installed) { Write-Log "Product not installed; nothing to do"; return }
    Write-Log "Found version $($installed.Version)"

    Write-Log "Backup: copying program files and registry hive"
    $stamp = Get-Date -Format yyyyMMdd-HHmm
    $backup = "C:\Backup\CVE-2020-3433-$stamp"
    New-Item -ItemType Directory -Force -Path $backup | Out-Null
    Copy-Item $installed.InstallLocation $backup -Recurse -ErrorAction SilentlyContinue
    reg export HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall "$backup\uninstall.reg" /y | Out-Null

    Write-Log "Upgrade: install patched build via vendor MSI / Windows Update"
    # Example MSI:  Start-Process msiexec.exe -ArgumentList '/i C:\Patches\Cisco AnyConnect Secure Mobility Client-patched.msi /qn /norestart' -Wait
    Install-WindowsUpdate -AcceptAll -AutoReboot -ErrorAction SilentlyContinue

    Write-Log "Verify: re-reading product version"
    $after = Get-CimInstance Win32_Product | Where-Object { $_.Name -match 'Cisco AnyConnect Secure Mobility Client' }
    Write-Log "Post-patch version: $($after.Version)"
    if ($after.Version -ne $installed.Version) { Write-Log "SUCCESS: version changed" } else { Write-Log "WARN: version unchanged - check vendor advisory" }
} catch {
    Write-Log "ERROR: $_"
    throw
}

Bash detect/upgrade/verify/log (Linux)


#!/usr/bin/env bash
# CVE-2020-3433 remediation runner. Re-runnable, exits non-zero on failure.
set -euo pipefail
log() { printf '%s %s\n' "$(date -Is)" "$*" | tee -a /var/log/cve-2020-3433-fix.log; }

log "Detect: current ciscoanyconnectsecuremobilityclient version"
if command -v dpkg >/dev/null 2>&1; then
    current=$(dpkg-query -W -f='${Version}' ciscoanyconnectsecuremobilityclient 2>/dev/null || echo "not-installed")
elif command -v rpm >/dev/null 2>&1; then
    current=$(rpm -q --qf '%{VERSION}-%{RELEASE}' ciscoanyconnectsecuremobilityclient 2>/dev/null || echo "not-installed")
else
    current="unknown"
fi
log "Current: $current"

log "Backup: snapshotting config"
backup="/var/backups/cve-2020-3433-$(date +%Y%m%d-%H%M)"
mkdir -p "$backup"
[ -d /etc/ciscoanyconnectsecuremobilityclient ] && cp -a /etc/ciscoanyconnectsecuremobilityclient "$backup/" || true

log "Upgrade: applying vendor patch"
if command -v apt-get >/dev/null 2>&1; then
    sudo apt-get update -qq
    sudo apt-get install -y --only-upgrade ciscoanyconnectsecuremobilityclient
elif command -v dnf >/dev/null 2>&1; then
    sudo dnf upgrade -y ciscoanyconnectsecuremobilityclient
elif command -v yum >/dev/null 2>&1; then
    sudo yum update -y ciscoanyconnectsecuremobilityclient
fi

log "Verify: re-reading ciscoanyconnectsecuremobilityclient version"
if command -v dpkg >/dev/null 2>&1; then
    after=$(dpkg-query -W -f='${Version}' ciscoanyconnectsecuremobilityclient)
else
    after=$(rpm -q --qf '%{VERSION}-%{RELEASE}' ciscoanyconnectsecuremobilityclient)
fi
log "After: $after"

if [ "$after" != "$current" ]; then
    log "SUCCESS: ciscoanyconnectsecuremobilityclient upgraded"
else
    log "WARN: version unchanged. Confirm the patched build is in your repository."
    exit 1
fi

After the upgrade, restart any service that loads the patched binary so the new code is actually running.

If you can't patch immediately

Patching is the only durable fix. These mitigations cut exposure while the change window is scheduled, they do not remove the vulnerability.

Restrict network exposure (iptables / nftables)


# Replace 10.0.0.0/8 with your management network. This drops everyone else.
sudo iptables -I INPUT -p tcp --dport 443 -s 10.0.0.0/8 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4


# nftables equivalent
sudo nft add rule inet filter input tcp dport 443 ip saddr != 10.0.0.0/8 drop

Windows: disable the vulnerable feature via registry


# Vendor advisory: https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-anyconnect-dll-F26WwJW
# Replace <Component> / <Setting> with the exact key from the vendor advisory.
# Always export the key first so you can roll back.
reg export "HKLM\SOFTWARE\Vendor\cisco anyconnect secure mobility client" "C:\Backup\preFix-CVE-2020-3433.reg" /y
Set-ItemProperty -Path "HKLM:\SOFTWARE\Vendor\cisco anyconnect secure mobility client" -Name "Disable<Setting>" -Value 1 -Type DWord
Restart-Service -Name "<service-name>" -Force

How to verify the fix worked

After applying the patched build, confirm the version string matches the fixed release named in the Cisco advisory.


dpkg -s ciscoanyconnectsecuremobilityclient | grep -i version       # Debian / Ubuntu
rpm -q ciscoanyconnectsecuremobilityclient                          # RHEL / Rocky


Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Run an authenticated vulnerability scan with a current signature set and confirm the scanner no longer flags CVE-2020-3433. For internet-facing deployments that were unpatched during the disclosure window, review logs for the affected endpoints over the full exposure period and rotate any credentials the vulnerable process could touch.

Frequently asked questions

Is CVE-2020-3433 being exploited in the wild?

Yes. CISA added CVE-2020-3433 to the Known Exploited Vulnerabilities catalog, which means active exploitation has been confirmed.

Will a firewall rule or WAF signature fully mitigate CVE-2020-3433?

No. Network-layer filters slow opportunistic scanners and block a subset of payloads, but a focused attacker who knows the bug will work around them. The vendor patch is the only durable fix.

Do I need to assume compromise if the affected service was internet-facing and unpatched?

For a CVE that CISA confirms is under active exploitation, yes. Review logs for the affected endpoints over the entire exposure window, rotate credentials the vulnerable process could read, and look for unexpected accounts, scheduled tasks, or outbound connections.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*