Pulsesecure vulnerabilities3 known to be exploited.

Vendor3 known exploited
The short answer

Pulsesecure has 93 published vulnerabilities across 20 products in our catalogue. 3 of them are on the list of flaws known to be exploited, so criminals are using them now. The most affected product is Pulse Connect Secure, with 57. If you run Pulsesecure software, patch the exploited flaws first.

See the exploited flaws

The most recent Pulsesecure flaw added to the known-exploited list is CVE-2020-8218, on 7 March 2022. We keep watching the known-exploited list.

Products

Which Pulsesecure products have the most vulnerabilities?

Pulse Connect Secure leads with 57 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.

Known exploited

Which Pulsesecure vulnerabilities are being exploited?

3 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 7.2
    CVE-2020-8218HighKnown exploited
    Pulse Connect Secure Code Injection Vulnerability

    A code injection vulnerability exists in Pulse Connect Secure that allows an attacker to crafted a URI to perform an arbitrary code execution via the admin web interface.

    Chance of use32%Known exploited since7 Mar 2022
  2. 7.2
    CVE-2019-11539HighKnown exploited
    Ivanti Pulse Connect Secure and Policy Secure Command Injection Vulnerability

    Ivanti Pulse Connect Secure and Policy Secure allows an authenticated attacker from the admin web interface to inject and execute commands.

    Chance of use99%Known exploited since3 Nov 2021
  3. 7.2
    CVE-2021-22900HighKnown exploited
    Ivanti Pulse Connect Secure Unrestricted File Upload Vulnerability

    Ivanti Pulse Connect Secure contains an unrestricted file upload vulnerability that allows an authenticated administrator to perform a file write via a maliciously crafted archive upload in the administrator web...

    Chance of use14%Known exploited since3 Nov 2021
Exploit likelihood

Which Pulsesecure 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.

50% or more10% to 49%Under 10%
  1. 99%

    Jonathan Looney discovered that the TCP_SKB_CB(skb)->tcp_gso_segs value was subject to an integer overflow in the Linux kernel when handling TCP Selective Acknowledgments (SACKs).

    CVSS7.5Published19 Jun 2019
  2. 99%
    CVE-2019-11539HighKnown exploited

    In Pulse Secure Pulse Connect Secure version 9.0RX before 9.0R3.4, 8.3RX before 8.3R7.1, 8.2RX before 8.2R12.1, and 8.1RX before 8.1R15.1 and Pulse Policy Secure version 9.0RX before 9.0R3.2, 5.4RX before 5.4R7.1,...

    CVSS7.2Published26 Apr 2019
  3. 95%

    Jonathan Looney discovered that the TCP retransmission queue implementation in tcp_fragment in the Linux kernel could be fragmented when handling certain TCP Selective Acknowledgment (SACK) sequences.

    CVSS7.5Published19 Jun 2019
  4. 82%

    The SSLv2 protocol, as used in OpenSSL before 1.0.1s and 1.0.2 before 1.0.2g and other products, requires a server to send a ServerVerify message before establishing that a client possesses certain plaintext RSA...

    CVSS5.9Published1 Mar 2016
  5. 69%

    A buffer overflow vulnerability exists in Windows File Resource Profiles in 9.X allows a remote authenticated user with privileges to browse SMB shares to execute arbitrary code as the root user.

    CVSS8.8Published27 May 2021
  6. 66%

    In Pulse Secure Pulse Connect Secure version 9.0RX before 9.0R3.4, 8.3RX before 8.3R7.1, 8.2RX before 8.2R12.1, and 8.1RX before 8.1R15.1 and Pulse Policy Secure version 9.0RX before 9.0R3.2, 5.4RX before 5.4R7.1,...

    CVSS7.2Published26 Apr 2019
  7. 45%

    Pulse Secure version 9.115 and below may be susceptible to client-side http request smuggling, When the application receives a POST request, it ignores the request's Content-Length header and leaves the POST body on...

    CVSS5.4Published30 Sep 2022
  8. 32%

    The fmtstr function in crypto/bio/b_print.c in OpenSSL 1.0.1 before 1.0.1s and 1.0.2 before 1.0.2g improperly calculates string lengths, which allows remote attackers to cause a denial of service (overflow and...

    CVSS9.8Published3 Mar 2016
  9. 32%
    CVE-2020-8218HighKnown exploited

    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.

    CVSS7.2Published30 Jul 2020
  10. 16%

    Artifex Ghostscript 9.25 and earlier allows attackers to bypass a sandbox protection mechanism via vectors involving the 1Policy operator.

    CVSS8.6Published19 Oct 2018
Precursor Intelligence

Running Pulsesecure? 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.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. 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.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

Our catalogue lists 93 published vulnerabilities across 20 products and 453 versions from Pulsesecure. The most recent Pulsesecure flaw added to the known-exploited list is CVE-2020-8218, on 7 March 2022.

3 Pulsesecure vulnerabilities are on the list of flaws known to be exploited. The most recently added are CVE-2020-8218, CVE-2019-11539 and CVE-2021-22900. The full list is on this page.

Pulse Connect Secure, with 57 published vulnerabilities. Its own page lists the ones known to be exploited.

Create a Precursor Intelligence account and track the Pulsesecure products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.