Threats / Ivanti / CVE-2019-11510
CVE-2019-11510
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-14
Ivanti Pulse Connect Secure vulnerability
Ivanti Pulse Connect Secure contains an arbitrary file read vulnerability allowing unauthenticated remote attackers to access sensitive files via crafted HTTPS requests.
Verdict
Today item, not a backlog item.
An unauthenticated attacker can read arbitrary files on affected Pulse Connect Secure instances without authentication. This vulnerability has been actively exploited in ransomware campaigns and poses critical risk to VPN infrastructure.
CISA KEV Yes · 2021-11-035Ransomware use Flagged5EPSS 0.99999 (verify live)6Exploit Weaponized · public PoC7CVSS 9.93CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
1005 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.99999 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.9 (CVSS:3.0/AC:L/AV:N/A:H/C:H/I:H/PR:L/S:C/UI:N) · Affected: Ivanti, Pulse Connect Secure. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.0, set at disclosure.
Weakness (CWE)
Mapped to CWE-22 Path Traversal — weakness family: Path traversal / file.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 910 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious URI targeting path traversal sequences to bypass file access restrictions on the Pulse Connect Secure appliance.
Business
Sensitive configuration files, credentials, and system data become accessible to unauthenticated threat actors.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I extract authentication tokens, encryption keys, and user credentials from readable system files to escalate my access.
Business
Compromised credentials enable lateral movement and persistent access to protected corporate networks and resources.
3
Lateral reach — past segmentation narrative 3
Attacker
I use obtained credentials and system information to deploy ransomware payloads across the internal network.
Business
Critical business systems are encrypted and held for ransom, causing operational shutdown and financial extortion losses.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by mitreCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.