CVE-2024-23897

From Exploited flaws, HARD’s guide to the flaws being used in attacks · Checked
This article is about a flaw in Jenkins Command Line Interface (CLI). For every flaw being used in attacks, see Exploited flaws; for Jenkins’s, see Jenkins flaws being used in attacks.

CVE-2024-23897 is a security flaw in Jenkins Command Line Interface (CLI). Attackers can run their own code on Jenkins Command Line Interface (CLI) from anywhere, without logging in. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 19 Aug 2024, and says ransomware gangs have used it.[1]

Jenkins Command Line Interface (CLI) is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff. Jenkins has published a fix or advice.

Description

CISA calls it a command line interface (CLI) path traversal in Jenkins Jenkins Command Line Interface (CLI). In its words: “Jenkins Command Line Interface (CLI) contains a path traversal vulnerability that allows attackers limited read access to certain files, which can lead to code execution.”[1]

The CVE record adds: “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.”[2]

The underlying weakness is CWE-27, in MITRE’s list of common software weaknesses.

It scores 9.8 out of 10 on the Common Vulnerability Scoring System, which rates it critical, scored by NVD using CVSS 3.1.[2]

Affected versions

NVD’s record doesn’t list version ranges for it; Jenkins’s advisory has them[3]. CISA names the product as Jenkins Jenkins Command Line Interface (CLI).

Most families won’t have Jenkins Command Line Interface (CLI); it’s for whoever looks after IT at work.

Exploitation

CISA added it to its catalog of known exploited vulnerabilities on 19 Aug 2024, 208 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 9 Sep 2024 to fix it.[1] CISA says ransomware gangs have used it.

FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at over 99%. That’s in the top 1% of the flaws it scores.[4]

CISA assesses it as automatable: attackers can run it against many targets at once.

CISA doesn’t say who was attacked, or how.

Fix

Jenkins has published a fix or advice.[3] CISA’s required action: “Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.”[1]

  1. Check whether you use it.Jenkins Command Line Interface (CLI) is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
  2. Send this page to your IT person.Ask them to confirm it’s fixed, or not in use. CISA gave US government agencies until 9 Sep 2024 to fix it.
  3. If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.

You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.

Timeline

DateEvent
The flaw is made public in the National Vulnerability Database, with a severity score of 9.8.[2]
CISA adds it to its catalog of flaws known to be used in attacks, noting that ransomware gangs have used it.[1]
CISA’s deadline for US government agencies to fix it.[1]
FIRST puts the odds of it being used in attacks in the next 30 days at over 99%.[4]

See also

Other Jenkins flaws

  • CVE-2017-1000353, Jenkins: remote code execution ·
  • CVE-2015-5317, Jenkins User Interface (UI): user interface (UI) information disclosure ·
  • CVE-2019-1003029, Jenkins Script Security Plugin: sandbox bypass ·
  • CVE-2019-1003030, Jenkins Matrix Project Plugin: remote code execution ·
  • CVE-2018-1000861, Jenkins Stapler Web Framework: stapler web framework deserialization of untrusted data ·

Every Jenkins flaw on CISA’s list · Everything added in August 2024

References

  1. ^ Cybersecurity and Infrastructure Security Agency. “Jenkins Command Line Interface (CLI) Path Traversal Vulnerability”. Known Exploited Vulnerabilities Catalog, added 19 Aug 2024.
  2. ^ National Institute of Standards and Technology. “CVE-2024-23897 Detail”. National Vulnerability Database, published 24 Jan 2024.
  3. ^ Jenkins. Advisories and fixes: jenkins.io.
  4. ^ FIRST. “Exploit Prediction Scoring System”. EPSS 1.000, percentile 100.0, 31 Oct 2026.
  5. CVE Program. “CVE-2024-23897”. The official CVE record.

This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.