{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:deployer-framework. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-36890 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:deployer-framework to 86.v7b_a_4a_55b_f3ec or later.","what":"CVE-2022-36890 is a medium-severity path traversal vulnerability in Jenkins Deployer Framework Plugin, published on 27 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-36890 and fix it if it is affected.\n\nWhat it is: CVE-2022-36890 is a medium-severity path traversal vulnerability in Jenkins Deployer Framework Plugin, published on 27 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-36890 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:deployer-framework (Maven): affected all versions; fixed in 86.v7b_a_4a_55b_f3ec\n- org.jenkins-ci.plugins:deployer-framework (Maven): affected all versions; fixed in 86.v7b_a_4a_55b_f3ec\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-2022-36890/ (Markdown: https://insights.sbomify.com/CVE-2022-36890/index.md)","id":"CVE-2022-36890","markdown":"https://insights.sbomify.com/CVE-2022-36890/index.md","name":"CVE-2022-36890","record":{"aliases":["GHSA-hgp9-2c4w-x9mh"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Deployer Plugin","requires_auth":"low_privilege","summary":"Attackers with Item/Read permission can check for the existence of arbitrary files on the Jenkins controller file system via the Deployer Framework Plugin.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"deployer_framework","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 Deployer Framework Plugin 85.v1d1888e8c021 and earlier does not restrict the name of files in methods implementing form validation, allowing attackers with Item/Read permission to check for the existence of an attacker-specified file path 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":true,"headline":"Jenkins Deployer Framework Plugin vulnerable to Path Traversal","id":"CVE-2022-36890","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"path_traversal","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"Jenkins Deployer Framework Plugin allows attackers with Item/Read permission to read deployment logs","id":"CVE-2022-36891"},"packages":[{"ecosystem":"Maven","fixed":["86.v7b_a_4a_55b_f3ec"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:deployer-framework","purl":null,"source":"GHSA-hgp9-2c4w-x9mh"},{"ecosystem":"Maven","fixed":["86.v7b_a_4a_55b_f3ec"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:deployer-framework","purl":"pkg:maven/org.jenkins-ci.plugins/deployer-framework","source":"GHSA-hgp9-2c4w-x9mh"}],"prev":{"headline":"Jenkins Deployer Framework Plugin does not restrict application path of applications when configuring a deployment","id":"CVE-2022-36889"},"products":["Jenkins Deployer Framework Plugin"],"published":"2022-07-27","related":[{"cvss_score":8.8,"headline":"Jenkins Deployer Framework Plugin does not restrict application path of applications when configuring a deployment","id":"CVE-2022-36889","kev_date_added":null,"published":"2022-07-27"},{"cvss_score":5.4,"headline":"Stored XSS vulnerability in Jenkins Deployer Framework Plugin","id":"CVE-2020-2227","kev_date_added":null,"published":"2020-07-15"},{"cvss_score":4.3,"headline":"Jenkins Deployer Framework Plugin allows attackers with Item/Read permission to read deployment logs","id":"CVE-2022-36891","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Jenkins project"]},"summary":"Attackers with Item/Read permission can check for the existence of arbitrary files on the Jenkins controller file system via the Deployer Framework Plugin.","url":"https://insights.sbomify.com/CVE-2022-36890/"}