What this checks: whether an Ivanti (Pulse Secure) Pulse Connect Secure host runs a version affected by unauth path-traversal arbitrary file read. Read-only: it fingerprints Ivanti (Pulse Secure) Pulse Connect Secure and reads the version, no exploitation.
3. Detection — reads the Ivanti (Pulse Secure) Pulse Connect Secure version from the version exposed at /dana-na/nc/nc_gina_ver.txt, compares to per branch: 8.2R12.1 (ProductVersion 8.2.12.64003) / 8.3R7.1 (8.3.7.65025) / 9.0R3.4 (9.0.3.64053); 8.1RX and below and 9.1R1 (9.1.1.1505) and above are not affected. Flags vulnerable on an affected build. No exploitation.
1. Target List — paste your Ivanti (Pulse Secure) Pulse Connect Secure URLs here, one per line (e.g. https://host.example.com).
Overview
This workflow finds Ivanti Pulse Connect Secure and sorts each host by whether its version falls below the CVE-2019-11510 fixed floors. CVE-2019-11510 is unauthenticated arbitrary file read through a path traversal on the VPN appliance. This check never walks a path traversal and never asks for a sensitive file. Give it hostnames, IP addresses, or URLs you are authorised to test. The workflow GETs /dana-na/nc/nc_gina_ver.txt only, fingerprints Pulse Connect Secure from that version text, reads the release string, and compares it to the 8.2R12.1, 8.3R7.1, and 9.0R3.4 floors in the graph. Every host comes back affected or not, so a fleet advisory becomes an evidenced list for exposure management. An affected row is a version signal only.
Run it on a schedule when edge VPN appliances lag on maintenance releases. A gateway frozen on 9.0R3.3 is the reason the same fingerprint stays useful.
Pipeline
Read the target list. Hosts, URLs, or ranges, one per line, become the scope.
GET /dana-na/nc/nc_gina_ver.txt on each host and fingerprint Pulse Connect Secure from the version text in that response.
Parse the release string and compare it to the CVE-2019-11510 floors in the graph (8.2R12.1, 8.3R7.1, 9.0R3.4).
Collect the per-host rows: product match, version, vulnerable flag, and any fetch error.
Emit the summary counts: hosts checked, product hits, vulnerable, and errors.
Inputs
Target scope. Hostnames, IP addresses, CIDR ranges, or URLs, one per line. Full URLs and host:port entries work too, since the workflow normalizes each into a bare host. Point it at scope you are authorised to test.
Outputs
results.jsonl. One row per host: URL, whether Pulse Connect Secure was detected, the version read, the vulnerable flag, and detail text.
findings.jsonl. The same per-host verdict shaped for triage, with severity set from the vulnerable flag.
summary.json. Counts across the list: targets, product hits, vulnerable, and errors, plus the detection notes from the graph.
Integrations
HTTP. Unauthenticated GET of /dana-na/nc/nc_gina_ver.txt only. No path traversal and no sensitive file read.
Sample output
The records below are illustrative and do not come from a real run. They show one Pulse Connect Secure host below a CVE-2019-11510 floor, one at or above its floor, and one host that is not the product.
Which Pulse Connect Secure versions does this flag?
Builds below the floors in the graph: 8.2R12.1, 8.3R7.1, and 9.0R3.4. The compare uses the version text /dana-na/nc/nc_gina_ver.txt itself served.
Does an affected row mean a sensitive file was read?
No. The check only GETs /dana-na/nc/nc_gina_ver.txt and reads the version string. It does not walk a path traversal and it does not confirm arbitrary file read.
Is this check safe on production?
Yes. It is a read-only unauthenticated GET of the public version endpoint. It does not authenticate or pull session data.
Does the check need credentials?
No. It fingerprints the public version text the way an external scanner would.
What is CVE-2019-11510?
Unauthenticated arbitrary file read in Ivanti Pulse Connect Secure through a path traversal. This workflow maps hosts to that CVE by version exposure only.