2020 · United States · O - Public administration and defence · Network intrusion and data theft via exploitation of Pulse Secure VPN appliances
Analysed 2026-11-06 by Hermes
Open this case in the tool →Network intrusion and data theft via exploitation of Pulse Secure VPN appliances
Expertise to Execution
Evidence coverage: 2/6 stages, weight 18/60
Decisive stage: entry (clearest evidence) · Alternative: Strategy to Execution
(1) The expectation at these victims - US government agencies and defense industrial base organisations whose remote access ran through internet-facing Pulse Secure VPN gateways - was operational: remediate published appliance vulnerabilities per vendor advisory and monitor the gateway, an expectation CISA later codified for federal agencies in Emergency Directive 21-03 (enumerate appliances, run the Integrity Tool even when fully patched, apply updates within 48 hours). (2) In practice, CISA documented compromises beginning in June 2020 or earlier in which initial access used CVE-2019-11510, CVE-2020-8260 and CVE-2020-8243 - flaws patched in 2019/2020 - alongside the newly disclosed zero-day CVE-2021-22893; the actors planted webshells providing authentication and MFA bypass and password logging, harvested credentials to move laterally as legitimate users, and maintained access for several months without detection, with victims confirming the compromise only after running the vendor Integrity Tool with CISA/Ivanti assistance. (3) That is a knowing-doing gap inside the material column: the remedy existed and was published years before the intrusions, and it failed in day-to-day operation of the exposed appliance estate (Expertise to Execution); nothing in the sources shows leadership informed and deferring (which would point to Strategy to Leadership or Expertise to Leadership) or a victim policy artefact that failed to translate (Strategy to Execution). The classification rests on the entry stage, whose origin and break are best documented by primary sources; the detection gap (months-long dwell, detection only via vendor tooling after external outreach) is load-bearing and points to the same type. The zero-day CVE-2021-22893 is explicitly not treated as a victim-side failing - it left no remediation window - and is not load-bearing for the type. RM18 (Expertise to Execution lens): the three VPN flaws were known and remediable via the 2019/2020 vendor advisories, yet remained exploitable on exposed appliances through 2020-2021, remediation having lagged across the appliance estate (causal role: Enabling). RM34 (Expertise to Execution lens): the victims' monitoring did not surface the webshells, credential logging or impossible-travel log patterns described in CISA's advisory, so detection came only when the vendor Integrity Tool was run months into the intrusion after CISA and Ivanti outreach (causal role: Obscuring). The documented persistence of the malware across software updates and factory resets amplified the impact but is not coded as a marker, since no source shows a specific victim's eradication attempt failing.
RM18 — Vulnerability / patch latencyRM34 — Monitoring / detection / alert-handling gapVictim is a diffuse multi-organisation campaign: the EuRepoC row names no receiver, only categories (government ministries, finance, defence industry; United States and Europe region), so the victim is named descriptively; Country set to United States as the campaign's primary focus (US DIB, CISA-confirmed US agency compromises) with additional Europe-region victims. Year taken from eurepoc_extra.start_date (01.08.2020); public disclosure was April 2021. Sector: receivers span government, finance and defence; one line chosen per the campaign's stated DIB/government focus. Attribution rests on technical reports by the IT-security community (Mandiant/FireEye), not an official government attribution. Source caveats: the row's Mandiant source_url no longer resolves to the April 2021 report (it redirects to a Google Cloud marketing page), and the original FireEye post could not be opened (fetch errors; the archive.org snapshot returned HTTP 429), so FireEye/Mandiant findings are cited as reported by SC Media and BleepingComputer. The Pulse Secure advisory blog.pulsesecure.net/pulse-connect-secure-security-update/ now redirects to the Ivanti copy, cited as opened. Two of the row's five source_urls describe adjacent campaigns and were not used for classification: the BleepingComputer Ivanti Connect Secure article (September 2024 campaign, UTA0178/UNC5221) and the Dark Reading Citrix ADC article.