cve.bz

CVE-2020-8254 pulsesecure pulse secure desktop client: Path traversal

8.8 highEPSS 2.4%

High (8.8) in pulsesecure pulse secure desktop client. EPSS 2.4% estimated probability of exploitation activity in the next 30 days.

On this page
A vulnerability in the Pulse Secure Desktop Client < 9.1R9 has Remote Code Execution (RCE) if users can be convinced to connect to a malicious server. This vulnerability only affects Windows PDC.To improve the security of connections between Pulse clients and Pulse Connect Secure, see below recommendation(s):Disable Dynamic certificate trust for PDC.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
2.4% (up from 2.1% a week ago; 2.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 84th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
CWE-23 Relative 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-8254 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-8254?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-8254?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-8254 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
pulsesecure:pulse_secure_desktop_clientbefore 9.1
pulsesecure:pulse_secure_desktop_client9.1:r1
pulsesecure:pulse_secure_desktop_client9.1:r2
pulsesecure:pulse_secure_desktop_client9.1:r3
pulsesecure:pulse_secure_desktop_client9.1:r3.1
pulsesecure:pulse_secure_desktop_client9.1:r4
pulsesecure:pulse_secure_desktop_client9.1:r4.1
pulsesecure:pulse_secure_desktop_client9.1:r4.2
pulsesecure:pulse_secure_desktop_client9.1:r5
pulsesecure:pulse_secure_desktop_client9.1:r6
pulsesecure:pulse_secure_desktop_client9.1:r7
pulsesecure:pulse_secure_desktop_client9.1:r7.1
pulsesecure:pulse_secure_desktop_client9.1:r8
pulsesecure:pulse_secure_desktop_client9.1:r8.2

Attack patterns (CAPEC)

  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-139 Relative Path Traversal Likelihood: High · Severity: High
  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: 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