CVE-2020-3153: Cisco AnyConnect Secure Mobility Client for Windows Uncontrolled Search Path Vulnerability
A vulnerability in the installer component of Cisco AnyConnect Secure Mobility Client for Windows could allow an authenticated local attacker to copy user-supplied files to system level directories with system level privileges. The vulnerability is due to the incorrect handling of directory paths. An attacker could exploit this vulnerability by creating a malicious file and copying the file to a system directory. An exploit could allow the attacker to copy malicious files to arbitrary locations with system level privileges. This could include DLL pre-loading, DLL hijacking, and other related attacks. To exploit this vulnerability, the attacker needs valid credentials on the Windows system.
Security readout for executives and security teams
Plain-English summary
Cisco AnyConnect for Windows contains an installer path-handling flaw that can let a logged-in local attacker place malicious files in protected locations using system-level privileges. This can enable later code-loading attacks. Although scored medium, CISA’s Known Exploited Vulnerabilities listing increases remediation urgency.
Executive priority
Prioritize remediation because CISA identifies active exploitation. Focus first on privileged, shared, administrative, and externally managed Windows endpoints. The valid-credential requirement reduces initial-access risk, but successful exploitation can enable system-level file placement and subsequent malicious code loading.
Technical view
CVE-2020-3153 is a CWE-427 uncontrolled search path vulnerability in the Windows installer component. An authenticated attacker with low privileges can copy supplied files into system-level directories, potentially enabling DLL pre-loading or hijacking. CVSS 3.0 is 6.5, with high integrity impact, changed scope, and no stated confidentiality or availability impact.
Likely exposure
Exposure is limited to Windows systems running affected Cisco AnyConnect Secure Mobility Client versions. The bundle does not identify exact affected or fixed versions. Exploitation requires valid local Windows credentials, so this is primarily a post-access privilege-escalation or persistence risk rather than remote initial access.
Exploitation context
CISA’s KEV status supports that this vulnerability has been exploited in the wild. The supplied evidence does not identify campaigns, threat actors, exploitation frequency, or ransomware use. No conclusion about public exploit availability should be drawn from this bundle.
Researcher notes
The vector is CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N. The supplied bundle establishes local authenticated exploitation and high integrity impact. Exact version boundaries, fixed releases, detection indicators, attack-chain details, and exploitation prevalence are not provided and should be verified through Cisco’s advisory.
Mitigation direction
Inventory Cisco AnyConnect installations and record their Windows client versions.
Consult Cisco’s advisory to determine affected and remediated releases for each deployment.
Apply Cisco-recommended remediation after confirming version and environment applicability.
Restrict unnecessary local and interactive access to systems running AnyConnect.
Monitor protected directories for suspicious DLLs or unexpected file creation.
Validation and detection
Compare every discovered AnyConnect version against Cisco’s current advisory.
Confirm remediated clients are installed across all managed Windows endpoints.
Check deployment records for failed, deferred, or offline endpoint updates.
Review endpoint telemetry for unusual files created in system directories.
Verify local access is limited according to operational requirements.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
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.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-427 · source CWE mapping
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.