VulnSocial

CVE-2019-11542(ivanti / connect_secure)

LOWCVSS 7.2 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

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, 5.3RX before 5.3R12.1, 5.2RX before 5.2R12.1, and 5.1RX before 5.1R15.1, an authenticated attacker (via the admin web interface) can send a specially crafted message resulting in a stack buffer overflow.

ivanti CVEsBack to dashboard
0.5/ 10 priority

Sources & remediation

Exploit / PoC references
Vendor / third-party advisories
Weakness type (CWE)
CWE-787

Priority

LOW

Exploitation

NONE

PoC

YES

Patch

NONE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • connect_secure
  • pulse_connect_secure
  • pulse_policy_secure

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • 1 total mentions across 1 day

Affected systems

Vendors
ivantipulsesecure
Products
connect_securepulse_connect_securepulse_policy_secure

91 versions affected across 3 products

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-10-05: 110-05
Referenced assets2 URLs
Full discourse1 post
  • Dino A. Dai Zovi@dinodaizovi

    Definitely amazing work, but the RCE vulnerability they exploited was the post-auth admin RCE CVE-2019-11539, not the memory corruption (CVE-2019-11542): https://x.com/i/chat https://devco.re/blog/2019/09/02/attacking-ssl-vpn-part-3-the-golden-Pulse-Secure-ssl-vpn-rce-chain-with-Twitter-as-case-study/ You can see in the blog post how they needed to crack the hash in order to exploit the RCE. In fact, we gave Orange Tsai a Pwnie Award in 2019 for this exact work (I co-founded the pwnie awards and was still involved with them back then).

    0000041
    39.6K followersView on X
CPE platform detail97 entries

97 of 97 entries

PartVendorProductVersionTarget SWTarget HW
Appivanticonnect_secure8.1--
Appivanticonnect_secure8.2--
Appivanticonnect_secure8.3--
Apppulsesecurepulse_connect_secure8.1r1.0--
Apppulsesecurepulse_connect_secure8.2r1.0--
Apppulsesecurepulse_connect_secure8.2r1.1--
Apppulsesecurepulse_connect_secure8.2r2.0--
Apppulsesecurepulse_connect_secure8.2r3.0--
Apppulsesecurepulse_connect_secure8.2r3.1--
Apppulsesecurepulse_connect_secure8.2r4.0--
Apppulsesecurepulse_connect_secure8.2r4.1--
Apppulsesecurepulse_connect_secure8.2r5.0--
Apppulsesecurepulse_connect_secure8.2r5.1--
Apppulsesecurepulse_connect_secure8.2r6.0--
Apppulsesecurepulse_connect_secure8.2r7.0--
Apppulsesecurepulse_connect_secure8.2r7.1--
Apppulsesecurepulse_connect_secure8.2rx--
Apppulsesecurepulse_connect_secure8.3rx--
Apppulsesecurepulse_connect_secure9.0r1--
Apppulsesecurepulse_connect_secure9.0r2--
Apppulsesecurepulse_connect_secure9.0r2.1--
Apppulsesecurepulse_connect_secure9.0r3--
Apppulsesecurepulse_connect_secure9.0r3.1--
Apppulsesecurepulse_connect_secure9.0r3.2--
Apppulsesecurepulse_connect_secure9.0rx--
Apppulsesecurepulse_policy_secure5.1r1.0--
Apppulsesecurepulse_policy_secure5.1r1.1--
Apppulsesecurepulse_policy_secure5.1r10.0--
Apppulsesecurepulse_policy_secure5.1r11.0--
Apppulsesecurepulse_policy_secure5.1r11.1--
Apppulsesecurepulse_policy_secure5.1r12.0--
Apppulsesecurepulse_policy_secure5.1r12.1--
Apppulsesecurepulse_policy_secure5.1r13.0--
Apppulsesecurepulse_policy_secure5.1r14.0--
Apppulsesecurepulse_policy_secure5.1r2.0--
Apppulsesecurepulse_policy_secure5.1r2.1--
Apppulsesecurepulse_policy_secure5.1r3.0--
Apppulsesecurepulse_policy_secure5.1r3.2--
Apppulsesecurepulse_policy_secure5.1r4.0--
Apppulsesecurepulse_policy_secure5.1r5.0--
Apppulsesecurepulse_policy_secure5.1r6.0--
Apppulsesecurepulse_policy_secure5.1r7.0--
Apppulsesecurepulse_policy_secure5.1r8.0--
Apppulsesecurepulse_policy_secure5.1r9.0--
Apppulsesecurepulse_policy_secure5.1r9.1--
Apppulsesecurepulse_policy_secure5.2r1.0--
Apppulsesecurepulse_policy_secure5.2r10.0--
Apppulsesecurepulse_policy_secure5.2r11.0--
Apppulsesecurepulse_policy_secure5.2r2.0--
Apppulsesecurepulse_policy_secure5.2r3.0--
Apppulsesecurepulse_policy_secure5.2r3.2--
Apppulsesecurepulse_policy_secure5.2r4.0--
Apppulsesecurepulse_policy_secure5.2r5.0--
Apppulsesecurepulse_policy_secure5.2r6.0--
Apppulsesecurepulse_policy_secure5.2r7.0--
Apppulsesecurepulse_policy_secure5.2r7.1--
Apppulsesecurepulse_policy_secure5.2r8.0--
Apppulsesecurepulse_policy_secure5.2r9.0--
Apppulsesecurepulse_policy_secure5.2r9.1--
Apppulsesecurepulse_policy_secure5.2rx--
Apppulsesecurepulse_policy_secure5.3r1.0--
Apppulsesecurepulse_policy_secure5.3r1.1--
Apppulsesecurepulse_policy_secure5.3r10.--
Apppulsesecurepulse_policy_secure5.3r11.0--
Apppulsesecurepulse_policy_secure5.3r12.0--
Apppulsesecurepulse_policy_secure5.3r2.0--
Apppulsesecurepulse_policy_secure5.3r3.0--
Apppulsesecurepulse_policy_secure5.3r3.1--
Apppulsesecurepulse_policy_secure5.3r4.0--
Apppulsesecurepulse_policy_secure5.3r4.1--
Apppulsesecurepulse_policy_secure5.3r5.0--
Apppulsesecurepulse_policy_secure5.3r5.1--
Apppulsesecurepulse_policy_secure5.3r5.2--
Apppulsesecurepulse_policy_secure5.3r6.0--
Apppulsesecurepulse_policy_secure5.3r7.0--
Apppulsesecurepulse_policy_secure5.3r8.0--
Apppulsesecurepulse_policy_secure5.3r8.1--
Apppulsesecurepulse_policy_secure5.3r8.2--
Apppulsesecurepulse_policy_secure5.3r9.0--
Apppulsesecurepulse_policy_secure5.3rx--
Apppulsesecurepulse_policy_secure5.4r1--
Apppulsesecurepulse_policy_secure5.4r2--
Apppulsesecurepulse_policy_secure5.4r2.1--
Apppulsesecurepulse_policy_secure5.4r3--
Apppulsesecurepulse_policy_secure5.4r4--
Apppulsesecurepulse_policy_secure5.4r5--
Apppulsesecurepulse_policy_secure5.4r5.2--
Apppulsesecurepulse_policy_secure5.4r6--
Apppulsesecurepulse_policy_secure5.4r6.1--
Apppulsesecurepulse_policy_secure5.4r7--
Apppulsesecurepulse_policy_secure5.4rx--
Apppulsesecurepulse_policy_secure9.0r1--
Apppulsesecurepulse_policy_secure9.0r2--
Apppulsesecurepulse_policy_secure9.0r2.1--
Apppulsesecurepulse_policy_secure9.0r3--
Apppulsesecurepulse_policy_secure9.0r3.1--
Apppulsesecurepulse_policy_secure9.0rx--

Explore more

Back to dashboardivanti CVEspulsesecure CVEsconnect_secure vulnerabilities