Security readout for executives and security teams
Plain-English summary
An attacker who already has valid credentials on a Windows computer could abuse Cisco AnyConnect to elevate their access to SYSTEM, the highest local privilege. This could enable full control of the device and its data. The issue is high severity and appears in CISA’s Known Exploited Vulnerabilities catalog.
Executive priority
Treat as a high-priority privilege-escalation issue because CISA identifies known exploitation and successful abuse grants SYSTEM privileges. Focus first on high-value Windows devices and environments where attackers could obtain local credentials. Do not assume every AnyConnect installation is vulnerable; establish version exposure using Cisco’s advisory.
Technical view
Insufficient runtime resource validation in the Windows AnyConnect IPC channel permits DLL hijacking through a crafted IPC message. Successful exploitation provides arbitrary code execution with SYSTEM privileges. CVSS 3.1 is 7.8 (local access, low complexity, low privileges, no user interaction), categorized as CWE-427.
Likely exposure
Exposure is limited to Windows systems running an affected Cisco AnyConnect Secure Mobility Client release. The supplied sources do not identify affected or fixed versions, so exposure cannot be determined from product presence alone. Exploitation requires authenticated local access, but converts low privileges into SYSTEM control.
Exploitation context
CISA’s KEV listing supports that this vulnerability has been exploited in the wild. It is not a remote, unauthenticated entry point: an attacker needs valid Windows credentials and local access. The supplied evidence does not describe exploitation frequency, targeted organizations, malware, or current campaign activity.
Researcher notes
The vulnerable boundary is an AnyConnect process IPC channel combined with insufficient validation of dynamically loaded resources. Preconditions are local attack vector, low privileges, and valid Windows credentials; user interaction is unnecessary. The source bundle provides no affected-version range, fixed-version details, exploitation artifacts, or indicators of compromise.
Mitigation direction
- Consult Cisco’s advisory for affected releases and the vendor-prescribed upgrade or remediation.
- Prioritize remediation on shared, privileged, administrative, and high-value Windows endpoints.
- Restrict unnecessary local access and promptly remove stale or compromised Windows credentials.
- Use endpoint controls to limit unauthorized DLL loading and detect privilege escalation.
Validation and detection
- Inventory Windows endpoints running Cisco AnyConnect Secure Mobility Client and record exact installed versions.
- Compare installed versions with Cisco’s advisory; the supplied bundle does not contain version boundaries.
- Confirm the vendor-prescribed remediation is deployed across affected endpoints.
- Review endpoint telemetry for suspicious AnyConnect IPC activity, DLL loading, or SYSTEM-level code execution.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-427: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-3433 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CISA KEV status
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9ciscoVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- Added to KEVCISA-ADP
CISA Known Exploited Vulnerabilities metadata lists this CVE as known exploited.
- ADP timelineCISA-ADP
CVE-2020-3433 added to CISA KEV
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2022-10-24T00:00:00.000Z: CVE-2020-3433 added to CISA KEV
Source materials
- CVE List V5 sourceCVE List V5
- 20200805 Cisco AnyConnect Secure Mobility Client for Windows DLL Hijacking VulnerabilityCVE reference, cisco · vendor-advisory, x_refsource_CISCO
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2020-3433CVE reference, CISA-ADP · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Uncontrolled Search Path Element
Uncontrolled Search Path Element represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.