{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:jobConfigHistory. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-41930 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:jobConfigHistory to 1229.v3039470161a_d or later.","what":"CVE-2023-41930 is a medium-severity path traversal vulnerability in Jenkins Job Configuration History Plugin, published on 6 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-41930 and fix it if it is affected.\n\nWhat it is: CVE-2023-41930 is a medium-severity path traversal vulnerability in Jenkins Job Configuration History Plugin, published on 6 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-41930 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:jobConfigHistory (Maven): affected all versions; fixed in 1229.v3039470161a_d\n- org.jenkins-ci.plugins:jobConfigHistory (Maven): affected all versions; fixed in 1229.v3039470161a_d\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-2023-41930/ (Markdown: https://insights.sbomify.com/CVE-2023-41930/index.md)","id":"CVE-2023-41930","markdown":"https://insights.sbomify.com/CVE-2023-41930/index.md","name":"CVE-2023-41930","record":{"aliases":["GHSA-c7r5-cww9-64q6"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins plugin","requires_auth":"low_privilege","summary":"Attackers can manipulate configuration history entries via the name parameter, potentially reading or modifying unauthorized data in Jenkins.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"job_configuration_history","vendor":"jenkins"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Jenkins Job Configuration History Plugin 1227.v7a_79fc4dc01f and earlier does not restrict the 'name' query parameter when rendering a history entry, allowing attackers to have Jenkins render a manipulated configuration history that was not created by the plugin.","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":true,"headline":"Path traversal in Jenkins Job Configuration History Plugin","id":"CVE-2023-41930","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"path_traversal","year":"2023"},"n_packages":2,"n_references":2,"next":{"headline":"XSS vulnerability in Jenkins Job Configuration History Plugin","id":"CVE-2023-41931"},"packages":[{"ecosystem":"Maven","fixed":["1229.v3039470161a_d"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:jobConfigHistory","purl":null,"source":"GHSA-c7r5-cww9-64q6"},{"ecosystem":"Maven","fixed":["1229.v3039470161a_d"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:jobConfigHistory","purl":"pkg:maven/org.jenkins-ci.plugins/jobConfigHistory","source":"GHSA-c7r5-cww9-64q6"}],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2023-41929"},"products":["Jenkins Job Configuration History Plugin"],"published":"2023-09-06","related":[{"cvss_score":8.8,"headline":"Job Configuration History Plugin's path traversal allows exploiting XXE vulnerability","id":"CVE-2023-41933","kev_date_added":null,"published":"2023-09-06"},{"cvss_score":6.5,"headline":"Path traversal allows exploiting XXE vulnerability in Jenkins Job Configuration History Plugin","id":"CVE-2023-41932","kev_date_added":null,"published":"2023-09-06"},{"cvss_score":5.4,"headline":"XSS vulnerability in Jenkins Job Configuration History Plugin","id":"CVE-2023-41931","kev_date_added":null,"published":"2023-09-06"},{"cvss_score":5.4,"headline":"Cross-site Scripting in Jenkins Job Configuration History Plugin","id":"CVE-2022-38664","kev_date_added":null,"published":"2022-08-23"},{"cvss_score":4.3,"headline":"Jenkins Job Configuration History Plugin doesn't redact encrypted values of secrets in job and agent configurations","id":"CVE-2026-57287","kev_date_added":null,"published":"2026-06-24"},{"cvss_score":4.3,"headline":"Jenkins Job Configuration History Plugin does not require POST requests for several HTTP endpoints","id":"CVE-2022-36887","kev_date_added":null,"published":"2022-07-27"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-26","vendors":["Jenkins Project"]},"summary":"Attackers can manipulate configuration history entries via the name parameter, potentially reading or modifying unauthorized data in Jenkins.","url":"https://insights.sbomify.com/CVE-2023-41930/"}