Reads a public app file through the known traversal. Advisory
Detect
Fingerprints ScreenConnect and flags CVE-2024-1708 by version.
Collect
Merges per-host detect and confirm rows.
Targets
Hosts, IPs, or URLs, one per line. Empty input uses localhost.
Overview
This workflow finds ConnectWise ScreenConnect and sorts each host by whether its version falls in the CVE-2024-1708 range. ScreenConnect is remote access into customer estates. CVE-2024-1708 is path traversal that CISA listed on KEV after mass exploitation in 2024. A below-23.9.8 console is the patch-lag you can prove from the login, not a guess from a hostname. Give it hostnames, IP addresses, or URLs you are authorised to test. The workflow fingerprints the product from the public page (title match on ScreenConnect), reads the version from / with a fallback to the root body, and compares that number to the range table in the graph. Every host comes back affected or not, so a fleet advisory becomes an evidenced list for exposure management. CVE-2024-1708 is on CISA KEV (known exploited). Version flag is first. Hosts in range get a second node that only reads a public app file through the known traversal. It does not read secrets or write files.
Run it on a schedule when the estate changes. New hosts and delayed patch windows are the reason the same check is worth more the second week than the first.
Pipeline
Read the target list. Hosts, URLs, or ranges, one per line, become the scope.
Fingerprint each host as ConnectWise ScreenConnect from the public page title, then GET / and parse the version. A host counts as affected only when the fingerprint matches and the version is inside the encoded range.
Confirm only those flagged hosts by reading a public app file through the known traversal.
Collect the per-host rows: product match, version, affected flag, confirmed flag, and any fetch error.
Emit the summary counts: hosts checked, product hits, affected, confirmed, and errors.
Inputs
Target list. Hostnames, IP addresses, CIDR ranges, or URLs, one per line. JSONL with a url field also works. Point it at scope you are authorised to test. Fingerprint is read-only GET. Confirm is a GET of a public app file, and only after the version flag.
Outputs
results.jsonl. One row per host: URL, whether ConnectWise ScreenConnect was detected, the version read, the affected flag, and whether the public-file confirm succeeded.
summary.json. Counts across the list: targets, product hits, affected, and errors.
Integrations
HTTP. Unauthenticated GET to the product root, /, and (on flagged hosts only) a public app file.
Sample output
The records below are illustrative and do not come from a real run. They show one ConnectWise ScreenConnect host inside the CVE-2024-1708 range, one patched host, and one host that is not the product.
Which ConnectWise ScreenConnect versions does this flag?
every build before 23.9.8. 23.9.8 and later is the floor the graph treats as not affected. The compare uses the version the product itself served.
Does a flagged host mean CVE-2024-1708 was exploited?
No. A flagged row is patch-lag against the range table. Confirm only tries to read a public app file. Treat a confirmed row as evidence the traversal still answers, not as proof someone already used it.
Is this check safe on production?
Yes. Fingerprint is read-only GET. Confirm is another GET of a public app file, only on hosts already in range. It does not log in, dump secrets, or write files.
Does the check need credentials?
No. It fingerprints the public page and reads / the way an external scanner would.
What is CVE-2024-1708?
Unauthenticated path traversal in ConnectWise ScreenConnect. CISA listed it on KEV after widespread 2024 exploitation. This workflow flags by version, then confirms with a public-file read.