cve.bz

CVE-2020-8218 Pulse Connect Secure Code Injection Vulnerability

7.2 highKEVExploit referenceEPSS 32%

High (7.2) in Pulse Secure Pulse Connect Secure. In CISA KEV since 2022-03-07. EPSS 32% estimated probability of exploitation activity in the next 30 days.

On this page
A code injection vulnerability exists in Pulse Connect Secure <9.1R8 that allows an attacker to crafted a URI to perform an arbitrary code execution via the admin web interface.

Severity

CVSS 3.1

7.2 high
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS
32% (unchanged from 32% a week ago; 32% 30 days ago) estimated probability of exploitation activity in the next 30 days; 98th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2022-03-07, due 2022-09-07
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2025-02-04. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-94 Improper Control of Generation of Code (Code Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2020-8218 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-8218?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-8218?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-8218 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
ivanti:connect_securethrough 9.0
ivanti:connect_secure9.1
ivanti:connect_secure9.1:r1
ivanti:connect_secure9.1:r2
ivanti:connect_secure9.1:r3
ivanti:connect_secure9.1:r4
ivanti:connect_secure9.1:r4.1
ivanti:connect_secure9.1:r4.2
ivanti:connect_secure9.1:r4.3
ivanti:connect_secure9.1:r5
ivanti:connect_secure9.1:r6
ivanti:connect_secure9.1:r7
ivanti:policy_secure9.1
ivanti:policy_secure9.1:r1
ivanti:policy_secure9.1:r2
ivanti:policy_secure9.1:r3
ivanti:policy_secure9.1:r3.1
ivanti:policy_secure9.1:r4
ivanti:policy_secure9.1:r4.1
ivanti:policy_secure9.1:r4.2
ivanti:policy_secure9.1:r5
ivanti:policy_secure9.1:r6
ivanti:policy_secure9.1:r7
pulsesecure:pulse_policy_securethrough 9.0

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

  • Emerging Threats Open ET EXPLOIT Possible Pulse Secure VPN RCE Inbound (CVE-2020-8218) sid 2030804

Attack patterns (CAPEC)

  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
  • CAPEC-242 Code Injection Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON