Assessment
Why it matters
CISA lists this vulnerability as known to be exploited; exploitation is confirmed; EPSS is 100.0%; technical severity is CVSS 10.0.
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 .
Who should care
- Teams operating Connect Secure, Pulse Connect Secure
- Vulnerability and exposure management teams
- Security operations teams monitoring exploitation activity
Response plan
What I would do
- Confirm whether Connect Secure, Pulse Connect Secure is present in the environment.
- Identify affected versions and establish whether vulnerable services are exposed or reachable.
- Apply updates per vendor instructions.
- Review relevant security telemetry for evidence of attempted or successful exploitation.
- Document the remediation decision and track it to verified completion.
Vendor remediation
Patch and remediation links
Use the vendor source below to confirm the correct fixed version, package or mitigation for your affected product.
Technical details
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- CWE
- CWE-22
- Affected versions
- Ivanti Connect Secure (Version: 9.0); Ivanti Pulse Connect Secure
- Published
- 8 May 2019
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
Signal timeline
- CVE published
- Added to CISA KEV
- Latest EPSS score: 100.0%
- Signal calculated at 88
External references
- Government advisory from www.cisa.gov
- Exploit information from packetstormsecurity.com
- Third-party advisory from packetstormsecurity.com
- Third-party advisory from www.securityfocus.com
- Exploit information from devco.re
- Third-party advisory from i.blackhat.com
- Vendor advisory from kb.pulsesecure.net
- Technical reference from lists.apache.org
- Third-party advisory from psirt.global.sonicwall.com
- Government advisory from www.kb.cert.org