Pulse Secure Desktop Client vulnerabilitiesRanked by how likely they are to be used.
Pulse Secure Desktop Client is made by Pulsesecure. We track 18 published vulnerabilities in it, across 69 versions. None of them is on the list of flaws known to be exploited today. If you run Pulse Secure Desktop Client, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Pulse Secure Desktop Client vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Pulse Secure Desktop Client's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Pulse Secure Desktop Client flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 2.8%CVE-2019-11213High
In Pulse Secure Pulse Desktop Client and Network Connect, an attacker could access session tokens to replay and spoof sessions, and as a result, gain unauthorized access as an end user, a related issue to CVE-2019-1573.
- 2.3%CVE-2020-8255Medium
A vulnerability in the Pulse Connect Secure < 9.1R9 admin web interface could allow an authenticated attacker to perform an arbitrary file reading vulnerability is fixed using encrypted URL blacklisting that prevents...
- 2.1%CVE-2020-8254High
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.
- 2.0%CVE-2020-8239Critical
A vulnerability in the Pulse Secure Desktop Client < 9.1R9 is vulnerable to the client registry privilege escalation attack.
- 1.7%CVE-2020-8241High
A vulnerability in the Pulse Secure Desktop Client < 9.1R9 could allow the attacker to perform a MITM Attack if end users are convinced to connect to a malicious server.
- 1.1%CVE-2018-20812High
An information exposure issue where IPv6 DNS traffic would be sent outside of the VPN tunnel (when Traffic Enforcement was enabled) exists in Pulse Secure Pulse Secure Desktop 9.0R1 and below.
- 0.9%CVE-2018-11002Medium
Pulse Secure Desktop Client 5.3 up to and including R6.0 build 1769 on Windows has Insecure Permissions.
- 0.8%CVE-2020-13162High
A time-of-check time-of-use vulnerability in PulseSecureService.exe in Pulse Secure Client versions prior to 9.1.6 down to 5.3 R70 for Windows (which runs as NT AUTHORITY/SYSTEM) allows unprivileged users to run a...
- 0.8%CVE-2020-15408Medium
An issue was discovered in Pulse Secure Pulse Connect Secure before 9.1R8.
- 0.7%CVE-2020-8263Medium
A vulnerability in the authenticated user web interface of Pulse Connect Secure < 9.1R9 could allow attackers to conduct Cross-Site Scripting (XSS) through the CGI file.
Running Pulse Secure Desktop Client? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
In Pulse Secure Pulse Desktop Client and Network Connect, an attacker could access session tokens to replay and spoof sessions, and as a result, gain unauthorized access as an end user, a related issue to CVE-2019-1573. (The endpoint would need to be already compromised for exploitation to succeed.) This affects Pulse Desktop Client 5.x before Secure Desktop 5.3R7 and Pulse Desktop Client 9.x before Secure Desktop 9.0R3. It also affects (for Network Connect customers) Pulse Connect Secure 8.1 before 8.1R14, 8.3 before 8.3R7, and 9.0 before 9.0R3.
- Matched to
- Pulse Secure Desktop Client on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 18 published vulnerabilities listed under the name Pulse Secure Desktop Client, across 69 versions.
None of Pulse Secure Desktop Client's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Pulse Secure Desktop Client. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.