Is CVE-2020-8218 exploited in the wild?

Yes. CVE-2020-8218 is known to be exploited in the wild, first recorded on 7 March 2022. Treat it as urgent.

How severe is CVE-2020-8218?

Critical severity, with a CVSS score of 7.2, published 7 March 2022.

Which products and versions are affected?

Pulse Secure Pulse Connect Secure < 9.1R8; Ivanti Connect Secure < 9.1R8.

Is there a fix for CVE-2020-8218?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2020-8218 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2020-8218?

Check whether you run Pulse Secure Pulse Connect Secure. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2020-8218: Pulse Connect Secure Code Injection Vulnerability

Q: Is there a fix for CVE-2020-8218?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2020-8218 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2020-8218?

Check whether you run Pulse Secure Pulse Connect Secure. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2020-8218 · Severity: critical · CVSS 7.2 · Exploited in the wild · Published 2022-03-07

A code injection vulnerability in Pulse Connect Secure (now Ivanti Connect Secure) allows an authenticated administrator to execute arbitrary code by crafting a specific URI via the admin web interface. The vulnerability affects versions prior to 9.1R8 and has been observed being exploited in the wild.

Quick answers

Is CVE-2020-8218 exploited in the wild?: Yes. CVE-2020-8218 is known to be exploited in the wild, first recorded on 7 March 2022. Treat it as urgent.
How severe is CVE-2020-8218?: Critical severity, with a CVSS score of 7.2, published 7 March 2022.
Which products and versions are affected?: Pulse Secure Pulse Connect Secure < 9.1R8; Ivanti Connect Secure < 9.1R8.
Is there a fix for CVE-2020-8218?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2020-8218 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2020-8218?: Check whether you run Pulse Secure Pulse Connect Secure. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Affected products

Pulse Secure Pulse Connect Secure < 9.1R8
Ivanti Connect Secure < 9.1R8

Timeline

2020-11-13: disclosed: Public blog post detailing the vulnerability published by GoSecure.
2022-03-07: kev added: Added to CISA's Known Exploited Vulnerabilities (KEV) catalog.

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.