dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 9 Sep 2024. Known ransomware use
JenkinsApplication

CVE-2024-23897

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-24
Fix available
A fix is available. Upgrade to 2.426.3 / 2.442 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Jenkins contains a CLI command parser that replaces '@' followed by a file path with the file's contents. This feature was not disabled by default in versions 2.441 and earlier (LTS 2.426.2 and earlier), allowing unauthenticated remote attackers to read arbitrary files on the Jenkins controller file system by sending specially crafted CLI commands.

MitigationUpgrade Jenkins to version 2.442 or LTS 2.426.3 or later, which disables the '@' character file expansion feature by default. If upgrade is not immediately possible, disable the Jenkins CLI entirely if not required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JenkinsApplication
Affected:< 2.426.3< 2.442

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Jenkins version
    Access the Jenkins web UI (look for /login or /api/json on port 8080) or check the Jenkins console log. The version is displayed on the bottom-right of the main page or in the system log startup output.
    Affected if The installed version is 2.441 or earlier, or LTS 2.426.2 or earlier.
  2. Confirm Jenkins CLI interface is accessible
    Check if the Jenkins CLI port (typically 50000 or configurable) is open and reachable, or if the /cli endpoint responds. Verify network exposure of CLI services.
    Affected if The CLI interface is reachable from untrusted networks without authentication.
  3. Locate CLI command parser configuration
    Examine the Jenkins configuration files (typically in jenkins.xml or via Manage Jenkins > CLI settings). Look for settings related to argument parsing or the '@' character handling in the CLI.
    Affected if The '@' argument file replacement feature is explicitly enabled in the CLI configuration.
  4. Test '@' argument file read behavior
    If CLI access is available, attempt a test command using '@' syntax (e.g., any-cli-command @/etc/passwd) to confirm whether file contents are being substituted into arguments.
    Affected if The '@' character triggers file content substitution, indicating the vulnerable parser behavior is active.

A user is affected if running Jenkins version 2.441 or earlier (or LTS 2.426.2 or earlier) AND the CLI interface is network-accessible AND the '@' argument file replacement feature is enabled in the CLI configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.426.3 / 2.442 or later
Fixed in 2.426.32.442
Interim mitigation

Upgrade Jenkins to version 2.442 or LTS 2.426.3 or later, which disables the '@' character file expansion feature by default. If upgrade is not immediately possible, disable the Jenkins CLI entirely if not required.

Recommended fix High confidence

Jenkins 2.426.3 (LTS) or Jenkins 2.442 (weekly)

  1. Upgrade Jenkins to version 2.426.3 (for LTS users) or version 2.442 (for weekly release users) or later
  2. After upgrading, verify the Jenkins service is running correctly
  3. Confirm the CLI parser '@' character behavior has been disabled in the new version
  4. Test that normal Jenkins functionality is unaffected
Caveat Standard Jenkins upgrade considerations apply; review LTS upgrade guide for major version jumps

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jenkins Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23897 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-23897 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data