cve.bz

CVE-2020-8222 Path traversal

6.8 mediumEPSS 2.6%

Medium (6.8). EPSS 2.6% estimated probability of exploitation activity in the next 30 days.

On this page
A path traversal vulnerability exists in Pulse Connect Secure <9.1R8 that allowed an authenticated attacker via the administrator web interface to perform an arbitrary file reading vulnerability through Meeting.

Severity

CVSS 3.1

6.8 medium
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
EPSS
2.6% (up from 2.3% a week ago; 2.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 86th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2020-8222 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-8222?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-8222?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-8222 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
ivanti:connect_secure9.1
ivanti:connect_secure9.1:r1
ivanti:connect_secure9.1:r2
ivanti:connect_secure9.1:r3
ivanti:connect_secure9.1:r4
ivanti:connect_secure9.1:r4.1
ivanti:connect_secure9.1:r4.2
ivanti:connect_secure9.1:r4.3
ivanti:connect_secure9.1:r5
ivanti:connect_secure9.1:r6
ivanti:connect_secure9.1:r7
pulsesecure:pulse_connect_securethrough 9.0
ivanti:policy_secure9.1
ivanti:policy_secure9.1:r1
ivanti:policy_secure9.1:r2
ivanti:policy_secure9.1:r3
ivanti:policy_secure9.1:r3.1
ivanti:policy_secure9.1:r4
ivanti:policy_secure9.1:r4.1
ivanti:policy_secure9.1:r4.2
ivanti:policy_secure9.1:r5
ivanti:policy_secure9.1:r6
ivanti:policy_secure9.1:r7
pulsesecure:pulse_policy_securethrough 9.0

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON