basicsecurity.net
Proof, not just disclosure.
Threats / Cisco / CVE-2020-3433
CVE-2020-3433 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Cisco AnyConnect Secure vulnerability

Cisco AnyConnect Secure Mobility Client for Windows contains an IPC channel vulnerability allowing authenticated attackers to execute arbitrary code with SYSTEM privileges through insufficient resource validation.

Verdict

Today item, not a backlog item.

An authenticated local attacker can exploit insufficient validation in the AnyConnect IPC mechanism to load malicious resources and achieve code execution with elevated SYSTEM privileges, enabling full system compromise.

CISA KEV Yes · 2022-10-243Ransomware use Flagged3EPSS 0.1013 (verify live)4Exploit Public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
2 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-10-24), flagged for known ransomware use.
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.1013 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Cisco, AnyConnect Secure. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-427 Uncontrolled Search Path.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I obtain valid Windows credentials for a target user or machine.
Business
Credential compromise or insider access creates initial attack surface.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I craft a malicious resource and place it where the AnyConnect IPC channel will load it at runtime.
Business
Insufficient validation controls allow arbitrary code injection into trusted application flow.
3

Lateral reach — past segmentation narrative 3

Attacker
I trigger the IPC channel to load my malicious resource, executing my code with SYSTEM privileges.
Business
Privilege escalation to SYSTEM level grants complete control over the endpoint and connected network resources.
4

Data at risk — exfiltration narrative 4

Attacker
I establish persistence and move laterally through the network using the compromised endpoint.
Business
VPN client compromise becomes a beachhead for enterprise network infiltration and data exfiltration.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • Ransomware-use flag (CISA)
  • EPSS probability (FIRST)
  • Public PoC available (VulnCheck)
  • 2 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by cisco (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by ciscoCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.