dbcve.org
Log CommandApplication · Jenkins

CVE-2024-23904

HIGH · 7.5 CVSS v3.1 Published 2024-01-24
Fix available
A fix is available. Upgrade to after 1.0.2 or later.
See remediation →
84/100
Remediation priority · High
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 Log Command Plugin 1.0.2 and earlier does not disable a feature of its command parser that replaces an '@' character followed by a file path in an argument with the file's contents, allowing unauthenticated attackers to read content from 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

The Jenkins Log Command Plugin versions 1.0.2 and earlier contains a command parser that by default interprets '@' followed by a file path as an instruction to replace that argument with the file's contents. This feature is not disabled, allowing unauthenticated attackers to read arbitrary files from the Jenkins controller filesystem by crafting requests with '@' prefixed paths.

MitigationUpgrade to a patched version of the Jenkins Log Command Plugin that disables this '@' file inclusion feature, or disable/remove the plugin until a patch is available.

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
Log CommandApplication
Affected:<= 1.0.2

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
None
Availability
None

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

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. Verify Jenkins Log Command Plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Log Command', or run this in the Jenkins script console: Jenkins.instance.pluginManager.plugins.findAll { it.shortName == 'log-command' }
    Affected if The plugin appears in the installed plugins list
  2. Determine the installed version of Log Command Plugin
    In the Installed plugins list, note the version number displayed next to Log Command Plugin, or run: Jenkins.instance.pluginManager.plugins.find { it.shortName == 'log-command' }.version
    Affected if The version is 1.0.2 or earlier (any version up to and including 1.0.2)
  3. Confirm the '@' file inclusion feature is enabled
    The vulnerability exists in the command parser of this plugin which interprets '@filepath' syntax. By default this feature is enabled. There is no configuration to disable it in affected versions. The feature is active whenever the plugin processes log command arguments.
    Affected if The plugin is installed and processing commands using its command parser (this is the default behavior in affected versions)
  4. Check if unauthenticated access to Jenkins is possible
    Verify that anonymous users have Overall/Read permission or access to the plugin's command endpoint. Go to Manage Jenkins > Configure Global Security > Authorization and check if 'Anonymous users' can access Jenkins, or inspect the security realm settings.
    Affected if Anonymous or unauthenticated users can access Jenkins or the specific plugin endpoint

You are affected if Jenkins Log Command Plugin version 1.0.2 or earlier is installed and the '@' file inclusion feature is active (enabled by default), allowing unauthenticated attackers to read arbitrary files via '@filepath' syntax in crafted requests.

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 a release after 1.0.2
Interim mitigation

Upgrade to a patched version of the Jenkins Log Command Plugin that disables this '@' file inclusion feature, or disable/remove the plugin until a patch is available.

Recommended fix Moderate confidence

Log Command Plugin 1.0.3 or later

  1. Navigate to the Jenkins dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Click on the 'Installed' tab
  4. Locate the 'Log Command' plugin in the list
  5. Check if version 1.0.3 or later is available in the 'Updates' tab
  6. If an update is available, select the Log Command plugin and click 'Update'
  7. Restart Jenkins if required after the update
  8. Verify the plugin has been updated to a version newer than 1.0.2

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

Fix this in Log Command Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23904 — 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-23904 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