CVE-2020-8218
Pulse Connect Secure Code Injection
- Published30 Jul 2020
- Added to CISA KEV7 Mar 2022
- Remediation due7 Sept 2022
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2020-8218 being actively exploited?
Yes. CVE-2020-8218 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 7 Mar 2022.
How severe is CVE-2020-8218?
CVE-2020-8218 has a CVSS 3.1 base score of 7.2, rated high. EPSS estimates a 32.3% probability of exploitation.
Which products are affected by CVE-2020-8218?
Affected products include Ivanti Connect Secure, Ivanti Policy Secure, Pulsesecure Pulse Policy Secure.
How do I fix CVE-2020-8218?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2020-8218 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, a risk for it never ranks below high, and the update that fixes it moves to the Emergency patch lane. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.