Proposal: Add Jenkins CLI CVE-2024-23897 detection module

I would like to propose adding a vulnerability detection module for:

CVE-2024-23897 – Jenkins CLI argument expansion arbitrary file read
Summary:
Jenkins versions ≤ 2.441 are vulnerable to arbitrary file read via @file argument expansion in the CLI. The issue is reachable pre-auth through the Jenkins CLI endpoint.
Behavioral Difference
In vulnerable versions:

help "@/etc/hosts"
causes /etc/hosts contents (e.g., 127.0.0.1 localhost) to appear in the response.
In patched versions (≥ 2.442):
ERROR: No such command @/etc/hosts.
No file content is reflected.

The difference is deterministic and safe to test.
Proposed Detection Approach
Confirm Jenkins presence (X-Jenkins header or /cli/).
Trigger safe probe using @/etc/hosts.
Flag vulnerable if common hosts file markers (127.0.0.1, localhost) appear in response.
No exploitation, no file writes, detection-only logic.
If this aligns with Nettacker’s scope, I would be happy to prepare a PR with a minimal, pure-HTTP implementation.

Please let me know if this would be acceptable..

Start by locating Nettacker’s existing Python vulnerability detection modules and the HTTP handling for Jenkins’ /cli/ endpoint. Use the proposed X-Jenkins header or /cli/ presence check, then review the safe @/etc/hosts probe behavior. Done means the module distinguishes vulnerable and patched Jenkins responses without exploitation or file writes.