cve.bz

CVE-2019-11539 Ivanti Pulse Connect Secure and Policy Secure Command Injection Vulnerability

7.2 highKEVExploitEPSS 99%

High (7.2) in Ivanti Pulse Connect Secure and Pulse Policy Secure. In CISA KEV since 2021-11-03, with known ransomware use. EPSS 99% estimated probability of exploitation activity in the next 30 days.

On this page
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, the admin web interface allows an authenticated attacker to inject and execute commands.

Severity

CVSS 3.1

7.2 high
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS
99% (unchanged from 99% a week ago; 99% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2021-11-03, due 2022-05-03, known ransomware use
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2025-02-03. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-78 Improper Neutralization of Special Elements used in an OS Command (OS Command Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2019-11539 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2019-11539?via=ask-ai-copy and https://cve.bz/cve/CVE-2019-11539?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2019-11539 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
ivanti:connect_secure8.1
ivanti:connect_secure8.1:r1.0
ivanti:connect_secure8.1:r1.1
ivanti:connect_secure8.1:r10.0
ivanti:connect_secure8.1:r11.0
ivanti:connect_secure8.1:r11.1
ivanti:connect_secure8.1:r12.0
ivanti:connect_secure8.1:r12.1
ivanti:connect_secure8.1:r13.0
ivanti:connect_secure8.1:r14.0
ivanti:connect_secure8.1:r2.0
ivanti:connect_secure8.1:r2.1
ivanti:connect_secure8.1:r3.0
ivanti:connect_secure8.1:r3.1
ivanti:connect_secure8.1:r3.2
ivanti:connect_secure8.1:r4.0
ivanti:connect_secure8.1:r4.1
ivanti:connect_secure8.1:r5.0
ivanti:connect_secure8.1:r6.0
ivanti:connect_secure8.1:r7
ivanti:connect_secure8.1:r7.0
ivanti:connect_secure8.1:r8.0
ivanti:connect_secure8.1:r9.0
ivanti:connect_secure8.1:r9.1
ivanti:connect_secure8.1:r9.2
ivanti:connect_secure8.2
ivanti:connect_secure8.2:r1
ivanti:connect_secure8.2:r1.0
ivanti:connect_secure8.2:r1.1
ivanti:connect_secure8.2:r10.0
ivanti:connect_secure8.2:r11.0
ivanti:connect_secure8.2:r12.0
ivanti:connect_secure8.2:r2.0
ivanti:connect_secure8.2:r3.0
ivanti:connect_secure8.2:r3.1
ivanti:connect_secure8.2:r4.0
ivanti:connect_secure8.2:r4.1
ivanti:connect_secure8.2:r5.0
ivanti:connect_secure8.2:r5.1
ivanti:connect_secure8.2:r6.0
ivanti:connect_secure8.2:r7.0
ivanti:connect_secure8.2:r7.1
ivanti:connect_secure8.2:r7.2
ivanti:connect_secure8.2:r8.0
ivanti:connect_secure8.2:r8.1
ivanti:connect_secure8.2:r8.2
ivanti:connect_secure8.2:r9.0
ivanti:connect_secure8.3
ivanti:connect_secure8.3:r1
ivanti:connect_secure8.3:r1.1
ivanti:connect_secure8.3:r2
ivanti:connect_secure8.3:r2.1
ivanti:connect_secure8.3:r3
ivanti:connect_secure8.3:r4
ivanti:connect_secure8.3:r5
ivanti:connect_secure8.3:r5.1
ivanti:connect_secure8.3:r5.2
ivanti:connect_secure8.3:r6
ivanti:connect_secure8.3:r6.1
ivanti:connect_secure8.3:r7
ivanti:connect_secure9.0:r1
ivanti:connect_secure9.0:r2
ivanti:connect_secure9.0:r2.1
ivanti:connect_secure9.0:r3
ivanti:connect_secure9.0:r3.1
ivanti:connect_secure9.0:r3.2
ivanti:connect_secure9.0:r3.3
ivanti:policy_secure9.0:r1
ivanti:policy_secure9.0:r2
ivanti:policy_secure9.0:r2.1
ivanti:policy_secure9.0:r3
ivanti:policy_secure9.0:r3.1
pulsesecure:pulse_policy_secure5.1r1.0
pulsesecure:pulse_policy_secure5.1r1.1
pulsesecure:pulse_policy_secure5.1r2.0
pulsesecure:pulse_policy_secure5.1r2.1
pulsesecure:pulse_policy_secure5.1r3.0
pulsesecure:pulse_policy_secure5.1r3.2
pulsesecure:pulse_policy_secure5.1r4.0
pulsesecure:pulse_policy_secure5.1r5.0
pulsesecure:pulse_policy_secure5.1r6.0
pulsesecure:pulse_policy_secure5.1r7.0
pulsesecure:pulse_policy_secure5.1r8.0
pulsesecure:pulse_policy_secure5.1r9.0
pulsesecure:pulse_policy_secure5.1r9.1
pulsesecure:pulse_policy_secure5.1r10.0
pulsesecure:pulse_policy_secure5.1r11.0
pulsesecure:pulse_policy_secure5.1r11.1
pulsesecure:pulse_policy_secure5.1r12.0
pulsesecure:pulse_policy_secure5.1r12.1
pulsesecure:pulse_policy_secure5.1r13.0
pulsesecure:pulse_policy_secure5.1r14.0
pulsesecure:pulse_policy_secure5.2r1.0
pulsesecure:pulse_policy_secure5.2r2.0
pulsesecure:pulse_policy_secure5.2r3.0
pulsesecure:pulse_policy_secure5.2r3.2
pulsesecure:pulse_policy_secure5.2r4.0
pulsesecure:pulse_policy_secure5.2r5.0
pulsesecure:pulse_policy_secure5.2r6.0
pulsesecure:pulse_policy_secure5.2r7.0
pulsesecure:pulse_policy_secure5.2r7.1
pulsesecure:pulse_policy_secure5.2r8.0
pulsesecure:pulse_policy_secure5.2r9.0
pulsesecure:pulse_policy_secure5.2r9.1
pulsesecure:pulse_policy_secure5.2r10.0
pulsesecure:pulse_policy_secure5.2r11.0
pulsesecure:pulse_policy_secure5.2rx
pulsesecure:pulse_policy_secure5.3r1.0
pulsesecure:pulse_policy_secure5.3r1.1
pulsesecure:pulse_policy_secure5.3r2.0
pulsesecure:pulse_policy_secure5.3r3.0
pulsesecure:pulse_policy_secure5.3r3.1
pulsesecure:pulse_policy_secure5.3r4.0
pulsesecure:pulse_policy_secure5.3r4.1
pulsesecure:pulse_policy_secure5.3r5.0
pulsesecure:pulse_policy_secure5.3r5.1
pulsesecure:pulse_policy_secure5.3r5.2
pulsesecure:pulse_policy_secure5.3r6.0
pulsesecure:pulse_policy_secure5.3r7.0
pulsesecure:pulse_policy_secure5.3r8.0
pulsesecure:pulse_policy_secure5.3r8.1
pulsesecure:pulse_policy_secure5.3r8.2
pulsesecure:pulse_policy_secure5.3r9.0
pulsesecure:pulse_policy_secure5.3r10.
pulsesecure:pulse_policy_secure5.3r11.0
pulsesecure:pulse_policy_secure5.3r12.0
pulsesecure:pulse_policy_secure5.3rx
pulsesecure:pulse_policy_secure5.4r1
pulsesecure:pulse_policy_secure5.4r2
pulsesecure:pulse_policy_secure5.4r2.1
pulsesecure:pulse_policy_secure5.4r3
pulsesecure:pulse_policy_secure5.4r4
pulsesecure:pulse_policy_secure5.4r5
pulsesecure:pulse_policy_secure5.4r5.2
pulsesecure:pulse_policy_secure5.4r6
pulsesecure:pulse_policy_secure5.4r6.1
pulsesecure:pulse_policy_secure5.4r7
pulsesecure:pulse_policy_secure5.4rx

Public exploits

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

  • Emerging Threats Open ET EXPLOIT Pulse Secure Post-Auth OS Command Injection (CVE-2019-11539) sid 2034014

Attack patterns (CAPEC)

  • CAPEC-6 Argument Injection Likelihood: High · Severity: High
  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-88 OS Command Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON