CVE-2024-23897: Jenkins Path Traversal Vulnerability Exploitation (CVE-2024-23897)
The short version: Jenkins 2.441 and earlier, LTS 2.426.2 and earlier does not disable a feature of its CLI command parser that replaces an '@' character followed by a file path in an argument with the file's contents, allowing unauthenticated attackers to read arbitrary files on the Jenkins controller file system. BreachRisk discovers exposed instances from your attack surface and flags this finding so you can prioritize by real-world breach risk.
At a glance
| Fact | Detail |
|---|---|
| Our severity take | High — BreachRisk score 6.9 (impact 4, likelihood 4) |
| CVSS v3.1 (NVD) | Unknown at time of writing |
| In CISA KEV? | Unknown at time of writing — check the KEV catalog |
| Known exploited? | Unknown at time of writing |
| Requires authenticated session? | Unknown at time of writing |
| CVE | CVE-2024-23897 |
What you need to know
Jenkins instance appears vulnerable to exploitation of path traversal vulnerability (CVE-2024-23897).
- How they find it — internet-facing exposure of the affected product is discoverable by routine scanning.
- How they use it — attackers exploit the vulnerability against reachable instances.
- What it leads to — compromise of the affected service and, depending on placement, a foothold for further movement.
How serious we see it
High — based on BreachRisk impact and likelihood scoring for this threat definition (score 6.9/9). Treat internet-facing instances as priority; confirm exposure and patch status before assuming you're clear.
Recommendations
- Upgrade Jenkins to any of the following versions that are patched for path traversal vulnerability CVE-2024-23897: 2.426.3, 2.442.
- Restrict access to affected host to trusted IP addresses until patch can be applied.
How BreachRisk sees it
BreachRisk discovers internet-facing assets tied to this threat, fingerprints the product where possible, and flags exposure for CVE-2024-23897. Where authorized, it can go beyond detection with a bounded, non-disruptive check rather than leaving you with a maybe. Continuous outside-in coverage means the exposed service is already on your radar ranked by how it actually gets used against you.