CVE-2020-8218
Published: March 7, 2022
Official Description
A code injection vulnerability exists in Pulse Connect Secure that allows an attacker to crafted a URI to perform an arbitrary code execution via the admin web interface.
CISA KEV Advisory
Pulse Connect Secure Code Injection Vulnerability
A code injection vulnerability exists in Pulse Connect Secure that allows an attacker to crafted a URI to perform an arbitrary code execution via the admin web interface.
Apply updates per vendor instructions.
Risk Analysis
This code injection vulnerability in Pulse Connect Secure allows an attacker to achieve arbitrary code execution via the admin web interface. By crafting a specific URI, an attacker can inject and execute malicious code. The high EPSS score of 0.91101 indicates a very high likelihood of exploitation, making this a critical vulnerability. Its presence in CISA's KEV catalog confirms it has been actively exploited.
This vulnerability is actively exploited in the wild. It is remotely exploitable, allowing attackers to execute code through the administrative interface.
Apply the latest security patches and updates for Pulse Connect Secure to address this code injection vulnerability. Restrict access to the admin web interface to trusted networks and users.
Technical Analysis
CVE-2020-8218 requires local access, meaning attackers must already have a foothold on the target system.
Exploitation requires some privileges, which limits the exposure to scenarios where an attacker has already gained initial access.
CISA has added CVE-2020-8218 to the Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation in the wild. U.S. federal agencies are required to patch this within the mandated timeframe, and all organizations should treat remediation as urgent.
Exploit & PoC Resources
All References (1)
Quick Facts
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2020-8218 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts
- !CISA KEV: Federal agencies must patch per BOD 22-01 timeline
- !Active exploitation confirmed — treat as P1