Threats / Jenkins / CVE-2024-23897
CVE-2024-23897
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
Jenkins Command Line Interface (CLI) vulnerability
Jenkins CLI path traversal vulnerability allows attackers to read sensitive files, potentially leading to code execution. Actively exploited in ransomware campaigns.
Verdict
Today item, not a backlog item.
A path traversal flaw in Jenkins Command Line Interface enables unauthorized file access that can be chained to achieve code execution. The vulnerability is under active exploitation and associated with ransomware operations.
CISA KEV Yes · 2024-08-194Ransomware use Flagged4EPSS 0.99999 (verify live)5Exploit Weaponized · public PoC6CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
444 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-08-19), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.99999 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Jenkins, Jenkins Command Line Interface (CLI). Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-27 CWE-27 — weakness family: Path traversal / file.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 208 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I exploit the path traversal to read Jenkins configuration files and credentials stored on the system.
Business
Attackers gain access to authentication tokens and system secrets, expanding their foothold.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I extract sensitive files that reveal deployment scripts, build configurations, or private keys.
Business
Compromised credentials and deployment artifacts enable lateral movement and supply chain compromise.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage the read access to identify code execution pathways through Jenkins job definitions or plugin configurations.
Business
Attackers achieve remote code execution on the Jenkins server and connected build infrastructure.
4
Data at risk — exfiltration narrative 4
Attacker
I execute ransomware payloads across the Jenkins environment and connected systems.
Business
Critical build and deployment infrastructure is encrypted, halting software delivery and operations.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by jenkinsCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.