CVE-2019-11510: Ivanti Pulse Connect Secure Arbitrary File Read
Ivanti Pulse Connect Secure · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.
- CVSS v3.0 (CVE record)
- 9.9
- critical
- EPSS (exploit probability, 30 days)
- >99.9%
- among the highest 0.1% of all CVEs
- Added to CISA KEV
- 2021-11-03
- US federal due date 2022-05-03
- Automatable (CISA SSVC)
- yes
- technical impact: total
CVE-2019-11510 explained
CVE-2019-11510 is a path traversal flaw in Ivanti Pulse Connect Secure (PCS), a product on the network devices platform. An unauthenticated remote attacker can send a specially crafted URI to read arbitrary files from the device. CISA lists it as known exploited, including in ransomware campaigns, so unpatched systems face real risk.
Impact
A remote attacker can read arbitrary files on the affected device by sending a crafted URI over the network, with low attack complexity and no user interaction. The description states no authentication is needed. CISA rates the flaw as automatable, so it can be exploited at scale, with total technical impact. The CVSS vector shows high impact on confidentiality, integrity and availability, with changed scope. Attackers are known to exploit it, including for ransomware.
Who is affected
The description names Pulse Secure Pulse Connect Secure (PCS) 8.2 before 8.2R12.1, 8.3 before 8.3R7.1, and 9.0 before 9.0R3.4. However, the structured CVE record for Ivanti Pulse Connect Secure lists no affected versions and names no fixed version. Check the vendor advisory to confirm which releases are affected and which contain the fix for your branch.
Written with AI from the data on this page and checked against it automatically.
Official description
In Pulse Secure Pulse Connect Secure (PCS) 8.2 before 8.2R12.1, 8.3 before 8.3R7.1, and 9.0 before 9.0R3.4, an unauthenticated remote attacker can send a specially crafted URI to perform an arbitrary file reading vulnerability .
CISA required action: Apply updates per vendor instructions.
CISA notes
- Reference CISA's ED 21-03 (cisa.gov/news-events/directives/ed-21-03-mitigate-pulse-c…) for further guidance and requirements. Note: The due date for addressing this vulnerability aligns with the requirements outlined in ED 21-03. nvd.nist.gov/vuln/detail/CVE-2019-11510
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: kb.pulsesecure.net
- CISA's deadline for US federal agencies: 2022-05-03 (passed) – a useful benchmark for everyone else, too.
What to do
- Follow the vendor advisory and apply updates per vendor instructions, as CISA requires.
- Upgrade each branch past the versions named in the description:
8.2R12.1,8.3R7.1or9.0R3.4, as confirmed by the vendor. - Restrict network exposure of the device's interfaces to trusted sources where possible.
- Check devices for signs of compromise, as the flaw is known to be exploited, including in ransomware attacks.
- Treat files readable on unpatched devices as potentially exposed and review them per your incident response process.
The CVE record names no fixed version in its structured data. Follow the vendor advisory to identify the correct fixed release and apply updates per vendor instructions, as CISA requires. Until patched, restrict network access to the device and monitor for signs of compromise.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- Yes – attackers can automate it at scale
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Questions about CVE-2019-11510
- Is CVE-2019-11510 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03 and notes known ransomware use. The US federal due date was 2022-05-03.
- Does an attacker need credentials?
- The description states that an unauthenticated remote attacker can exploit the flaw by sending a specially crafted URI. CISA rates it as automatable.
- Which versions fix the issue?
- The description implies fixes at
8.2R12.1,8.3R7.1and9.0R3.4for their branches, but the structured CVE record names no fixed version. Confirm with the vendor advisory.
Written with AI from the data on this page and checked against it automatically.
References
Other advisories
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.