Pulse Policy Secure vulnerabilitiesAnd the versions its exploited flaws hit.
Pulse Policy Secure is made by Pulsesecure. We track 31 published vulnerabilities in it, across 82 versions. 2 of them are on the list of flaws known to be exploited, the newest added on 7 March 2022. If you run Pulse Policy Secure, check your version against the exploited flaws below and patch those first.
The most recent Pulse Policy Secure flaw added to the known-exploited list is CVE-2020-8218, on 7 March 2022. We keep watching the known-exploited list.
Which versions of Pulse Policy Secure do the exploited flaws hit?
Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.
- CVE-2020-8218Exploited list, 7 Mar 2022
Pulse Connect Secure Code Injection Vulnerability
up to 9.0 - CVE-2019-11539Exploited list, 3 Nov 2021
Ivanti Pulse Connect Secure and Policy Secure Command Injection Vulnerability
5.1r1.05.1r1.15.1r2.05.1r2.15.1r3.05.1r3.25.1r4.05.1r5.0
Which Pulse Policy Secure vulnerabilities are being exploited?
2 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.
- 7.2Pulse 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.
- 7.2Ivanti 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.
Which Pulse Policy Secure 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.
- 99%CVE-2019-11477High
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).
- 99%
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,...
- 95%CVE-2019-11478High
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.
- 66%CVE-2019-11542High
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,...
- 32%
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.
- 9.8%CVE-2020-11581High
An issue was discovered in Pulse Secure Pulse Connect Secure (PCS) through 2020-04-06.
- 7.7%CVE-2019-11540Critical
In Pulse Secure Pulse Connect Secure version 9.0RX before 9.0R3.4 and 8.3RX before 8.3R7.1 and Pulse Policy Secure version 9.0RX before 9.0R3.2 and 5.4RX before 5.4R7.1, an unauthenticated, remote attacker can...
- 7.7%CVE-2019-11509High
In Pulse Secure Pulse Connect Secure (PCS) before 8.1R15.1, 8.2 before 8.2R12.1, 8.3 before 8.3R7.1, and 9.0 before 9.0R3.4 and Pulse Policy Secure (PPS) before 5.1R15.1, 5.2 before 5.2R12.1, 5.3 before 5.3R15.1, 5.4...
- 4.1%CVE-2018-6320Critical
A vulnerability has been discovered in login.cgi in Pulse Secure Pulse Connect Secure (PCS) 8.1RX before 8.1R12 and 8.3RX before 8.3R2 and Pulse Policy Secure (PPS) 5.2RX before 5.2R9 and 5.4RX before 5.4R2 wherein...
- 3.2%CVE-2020-15352High
An XML external entity (XXE) vulnerability in Pulse Connect Secure (PCS) before 9.1R9 and Pulse Policy Secure (PPS) before 9.1R9 allows remote authenticated admins to conduct server-side request forgery (SSRF)...
Running Pulse Policy Secure? 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 flaw being exploited affects software Acme tracks
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.
- Matched to
- Pulse Policy Secure on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 31 published vulnerabilities listed under the name Pulse Policy Secure, across 82 versions. The most recent Pulse Policy Secure flaw added to the known-exploited list is CVE-2020-8218, on 7 March 2022.
2 are on the list of flaws known to be exploited. The most recently added are CVE-2020-8218 and CVE-2019-11539.
Each flaw names its own versions, usually as ranges. The newest, CVE-2020-8218, affects up to 9.0. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Pulse Policy Secure. 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.