Skip to content
Fencer Intel
high 7.2

CVE-2020-8218 kev in the critical feed json

A code injection vulnerability exists in Pulse Connect Secure <9.1R8 that allows an attacker to crafted a URI to perform an arbitrary code…

published 6y ago modified 4mo ago also EUVD-2020-29091

cvss
7.2
version 3.1, CNA
cisa kev
Exploited
added 2022-03-07
epss
32.3%
EPSS 32.3% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

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.

Patch / fix

cisa required action Apply updates per vendor instructions.

Is CVE-2020-8218 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Published
  2. Added to CISA KEV
  3. CISA patch deadline
  4. CISA SSVC: exploitation active

Known exploited

Added
4y ago
Patch by
2022-09-07 (4y ago)
Ransomware
Not known
Required action
Apply updates per vendor instructions.
Vendor, product
Pulse Secure, Pulse Connect Secure
CISA name
Pulse Connect Secure Code Injection Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

32.25% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • gosecure.net https://www.gosecure.net/blog/2020/11/13/forget-your-perimeter-part-2-four-vulnerabilities-in-pulse-connect-secure/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CISA ADP 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P

Affected products

  • n/a Pulse Connect Secure

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.