# CVE-2020-8243: Ivanti Pulse Connect Secure Code Execution Vulnerability

- Exploited (CISA KEV): yes, added 2021-11-03
- Published: 2020-09-29
- CVSS: 7.2 HIGH (v3.1)
- EPSS: 90.8% (100th percentile)
- CWE: CWE-94

A vulnerability in the Pulse Connect Secure < 9.1R8.2 admin web interface could allow an authenticated attacker to upload custom template to perform an arbitrary code execution.

## Edge WAF coverage (claimed by vendors, not measured)

| Vendor | Status | First rule | Days after publication |
|---|---|---|---|
| Cloudflare | Before feed history | — | — |
| AWS | No public claim | — | — |
| Microsoft Azure | Rule published | — | — |
| Google Cloud | Before feed history | — | — |
| Fastly | Before feed history | — | — |
| F5 | Before feed history | — | — |
| Akamai | No public source | — | — |
| OWASP CRS | Before feed history | — | — |

### Microsoft Azure

- undated · listed · rule 99001004
  > Rule 99001004: Critical - 5 · 2 · Attempted Pulse Secure custom template exploitation CVE-2020-8243
  Source: https://learn.microsoft.com/en-us/azure/web-application-firewall/afds/waf-front-door-drs
- undated · listed · rule 99001004
  > Rule 99001004: Critical - 5 · 2 · Attempted Pulse Secure custom template exploitation CVE-2020-8243
  Source: https://learn.microsoft.com/en-us/azure/web-application-firewall/ag/application-gateway-crs-rulegroups-rules

"No public claim" means no vendor statement names this CVE; "Before feed history" means the CVE is older than the vendor feed. In both cases generic rules may still block it.

HTML: https://cve.vigilbase.com/cve/CVE-2020-8243 · JSON: https://cve.vigilbase.com/api/v1/cves/CVE-2020-8243