What this checks: whether a Jenkins host runs a version affected by unauth information disclosure via Fingerprints pages. Read-only: it fingerprints Jenkins and reads the version, no exploitation.
3. Detection — reads the Jenkins version from the product's default response and version banner, compares to 1.638 (weekly) / 1.625.2 (LTS 1.625.x line). Flags vulnerable on an affected build. No exploitation.
1. Target List — paste your Jenkins URLs here, one per line (e.g. https://host.example.com).
Overview
This workflow finds Jenkins and sorts each host by whether its version falls below the CVE-2015-5317 fixed floors. CVE-2015-5317 is unauthenticated information disclosure through Fingerprints pages on vulnerable Jenkins builds. This check never browses the Fingerprints UI and never exercises a write path. Give it hostnames, IP addresses, or URLs you are authorised to test. The workflow fingerprints Jenkins from the product default response and version banner, parses the version, and compares it to the weekly and LTS 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 CI controllers turn over. A restored weekly build that still sits under 1.638 is the reason the same fingerprint stays useful.
Pipeline
Read the target list. Hosts, URLs, or ranges, one per line, become the scope.
Fetch each host and fingerprint Jenkins from the product default response and version banner.
Parse the version and compare it to the CVE-2015-5317 floors in the graph.
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 Jenkins 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 fingerprint of the product default response and version banner only. No Fingerprints page browse and no write path.
Sample output
The records below are illustrative and do not come from a real run. They show one Jenkins host below a CVE-2015-5317 floor, one at or above its line floor, and one host that is not the product.
Builds below the floors in the graph: 1.638 on the weekly line and 1.625.2 on the LTS 1.625.x line. A version picks the matching line, then compares to that line floor. The compare uses the version the default response and banner themselves served.
Does an affected row mean Fingerprints disclosure worked?
No. The check only fingerprints Jenkins and reads the version. It does not open Fingerprints pages, does not authenticate, and does not confirm disclosure.
Is this check safe on production?
Yes. It is a read-only unauthenticated HTTP fingerprint of the public product response. It does not write job or fingerprint data.
Does the check need credentials?
No. It fingerprints the public default response the way an external scanner would.
What is CVE-2015-5317?
Unauthenticated information disclosure via Fingerprints pages on vulnerable Jenkins builds. This workflow maps hosts to that CVE by version exposure only.