CVE-2020-8254 Path traversal in Pulse Secure Desktop Client
Attackers can achieve remote code execution on Windows clients by tricking users into connecting to a malicious server, mitigated by disabling dynamic certificate trust.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2020-8254?
CVE-2020-8254 is a high-severity path traversal vulnerability in Pulse Secure Desktop Client, published on 28 Oct 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
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.
Which versions are affected by CVE-2020-8254?
It affects 1 product.
Products include Pulsesecure Pulse Secure Desktop Client.
How do I fix CVE-2020-8254?
No fix has been published for CVE-2020-8254 yet. Limit exposure of the affected software until one is available.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2020-8254 being exploited?
There is no known exploitation of CVE-2020-8254 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Other vulnerabilities in Pulse Secure Desktop Client
- CVE-2020-8239 Privilege escalation in Pulse Secure Desktop Cient
- CVE-2020-8240 Privilege escalation in Pulse Secure Desktop Client
- CVE-2020-8248 Privilege escalation in Pulse Secure Desktop Client
- CVE-2020-8249 Memory corruption in Pulse Secure Desktop Client
- CVE-2020-8250 Privilege escalation in Pulse Secure Desktop Client
Sources
Also known as GHSA-p993-j26m-6v98.