CASCACascade Atlas

Evidence dossier

CVE-2020-3433

Cisco AnyConnect Secure Mobility Client for Windows DLL Hijacking Vulnerability

64.3–80.8Priority evidence range
As known Jul 19, 2026, 5:00 AM UTCgen-56ccdaf9

Normalized restatement

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. An attacker could exploit this vulnerability by sending a crafted IPC message to the AnyConnect process. A successful exploit could allow the attacker to execute arbitrary code on the affected machine with SYSTEM privileges. To exploit this vulnerability, the attacker would need to have valid credentials on the Windows system.

State
PUBLISHED
Published
Aug 17, 2020
Updated
Oct 21, 2025
Evidence coverage
85%
CISA KEVCatalog member

Apply updates per vendor instructions.

FIRST EPSS10.05%

2026-07-18 · v2026.06.15 · percentile 95.1%

Source stateNo scored conflict

Distinct CVSS assessments remain side by side; none are averaged.

Source comparison

Who said what

CISA-ADPindependent enrichment
container

CISA ADP Vulnrichment

ciscooriginal assertion
container

Cisco AnyConnect Secure Mobility Client for Windows DLL Hijacking Vulnerability

CVEderivative copy
container

CVE Program Container

CISA KEVoriginal assertion
observed_exploitation

Cisco AnyConnect Secure Mobility Client for Windows DLL Hijacking Vulnerability

FIRST EPSSoriginal assertion
model_probability

Probability 0.100490000000; percentile 0.951010000000

Applicability

Cited product scope

Trace impact →
CiscoCisco AnyConnect Secure Mobility Client
[{"status": "affected", "version": "n/a"}]unknown
Unknown vendorUnknown product
cpe:2.3:a:cisco:anyconnect_secure_mobility_client:*:*:*:*:*:windows:*:*; end excluding 4.9.00086supported

Assessments

CVSS by origin

7.8
nvd@nist.govCVSS 3.1 · role PrimaryCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
7.2
nvd@nist.govCVSS 2.0 · role PrimaryAV:L/AC:L/Au:N/C:C/I:C/A:C
7.8
psirt@cisco.comCVSS 3.1 · role SecondaryCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
7.8
ciscoCVSS 3.1 · role unknownCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Limitations and unknowns

  • KEV membership is authoritative for the catalog, not proof of exposure in any environment.
  • EPSS is a dated model probability and not an individual-environment prediction.
  • Affected or fixed status applies only to the exact cited product and version scope; unresolved scope remains unknown.
  • NVD-carried upstream facts remain derivative and are not independent corroboration.
  • Only NVD metrics validated under the generation-bound calculator are Public Priority eligible; direct CVE record metrics remain display-only.
  • NVD CVSS source eligibility is closed: NVD-authored, exact record-source, or registered same-CVE container origin; unmapped sources remain display-only.
  • Factor D is unknown in Public Core because no accepted canonical mapping-obligation ledger is present.
  • Core replay supports the active and immediately prior generation; retrospective valid-at replay is deferred.