{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:log-command. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-23904 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-23904 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-23904 is a high-severity path traversal vulnerability in Jenkins Log Command Plugin, published on 24 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-23904 and fix it if it is affected.\n\nWhat it is: CVE-2024-23904 is a high-severity path traversal vulnerability in Jenkins Log Command Plugin, published on 24 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-23904 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:log-command (Maven): affected all versions up to 1.0.2; no fix listed\n- org.jenkins-ci.plugins:log-command (Maven): affected all versions up to 1.0.2; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-23904/ (Markdown: https://insights.sbomify.com/CVE-2024-23904/index.md)","id":"CVE-2024-23904","markdown":"https://insights.sbomify.com/CVE-2024-23904/index.md","name":"CVE-2024-23904","record":{"aliases":["GHSA-qjpf-2jhx-3758"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Log Command Plugin","requires_auth":"none","summary":"Unauthenticated attackers can read arbitrary files on the Jenkins controller by exploiting a file path replacement feature in the Log Command Plugin.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"log_command","vendor":"jenkins"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Arbitrary file read vulnerability in Jenkins Log Command Plugin","id":"CVE-2024-23904","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"path_traversal","year":"2024"},"n_packages":2,"n_references":2,"next":{"headline":"Content-Security-Policy disabled by Red Hat Dependency Analytics Jenkins Plugin","id":"CVE-2024-23905"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.0.2"],"package":"org.jenkins-ci.plugins:log-command","purl":null,"source":"GHSA-qjpf-2jhx-3758"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.0.2"],"package":"org.jenkins-ci.plugins:log-command","purl":"pkg:maven/org.jenkins-ci.plugins/log-command","source":"GHSA-qjpf-2jhx-3758"}],"prev":{"headline":"Non-constant time webhook token comparison in Jenkins GitLab Branch Source Plugin","id":"CVE-2024-23903"},"products":["Jenkins Log Command Plugin"],"published":"2024-01-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-20","vendors":["Jenkins Project"]},"summary":"Unauthenticated attackers can read arbitrary files on the Jenkins controller by exploiting a file path replacement feature in the Log Command Plugin.","url":"https://insights.sbomify.com/CVE-2024-23904/"}