Is CVE-2020-8243 exploited in the wild?

Yes. CVE-2020-8243 is known to be exploited in the wild, first recorded on 3 November 2021. Treat it as urgent.

How severe is CVE-2020-8243?

Critical severity, with a CVSS score of 7.2, published 3 November 2021.

Which products and versions are affected?

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

Is there a fix for CVE-2020-8243?

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-8243 attacked?

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

Am I affected by CVE-2020-8243?

Check whether anything you run is named in the advisory. 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-8243: Ivanti Pulse Connect Secure Code Execution Vulnerability

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

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-8243 attacked?

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

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

Check whether anything you run is named in the advisory. 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-8243 · Severity: critical · CVSS 7.2 · Exploited in the wild · Published 2021-11-03

A vulnerability in the Ivanti Pulse Connect Secure admin web interface allows an authenticated attacker with high privileges to upload a custom template. This can be leveraged to achieve arbitrary code execution on the underlying system.

Quick answers

Is CVE-2020-8243 exploited in the wild?: Yes. CVE-2020-8243 is known to be exploited in the wild, first recorded on 3 November 2021. Treat it as urgent.
How severe is CVE-2020-8243?: Critical severity, with a CVSS score of 7.2, published 3 November 2021.
Which products and versions are affected?: Ivanti Pulse Connect Secure < 9.1R8.2; Ivanti Pulse Policy Secure < 9.1R8.2.
Is there a fix for CVE-2020-8243?: 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-8243 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2020-8243?: Check whether anything you run is named in the advisory. 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

Ivanti Pulse Connect Secure < 9.1R8.2
Ivanti Pulse Policy Secure < 9.1R8.2

Timeline

2021-11-03: disclosed
2021-11-03: kev added: Added to CISA Known Exploited Vulnerabilities Catalog
2021-11-03: advisory: NVD publication date

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