{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:pipeline-input-step. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-34177 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:pipeline-input-step to 449.v77f0e8b or later.","what":"CVE-2022-34177 is a high-severity path traversal vulnerability in Jenkins Pipeline: Input Step Plugin, published on 22 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-34177 and fix it if it is affected.\n\nWhat it is: CVE-2022-34177 is a high-severity path traversal vulnerability in Jenkins Pipeline: Input Step Plugin, published on 22 Jun 2022. 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-2022-34177 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:pipeline-input-step (Maven): affected all versions; fixed in 449.v77f0e8b\n- org.jenkins-ci.plugins:pipeline-input-step (Maven): affected all versions; fixed in 449.v77f0e8b\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-34177/ (Markdown: https://insights.sbomify.com/CVE-2022-34177/index.md)","id":"CVE-2022-34177","markdown":"https://insights.sbomify.com/CVE-2022-34177/index.md","name":"CVE-2022-34177","record":{"aliases":["GHSA-29q6-p2cg-4v23","RHSA-2022:9110"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Pipeline plugin","requires_auth":"none","summary":"Attackers can create or replace arbitrary files on the Jenkins controller by exploiting unsanitized parameter names in Pipeline input steps.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"pipeline\\","vendor":"jenkins"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Jenkins Pipeline: Input Step Plugin 448.v37cea_9a_10a_70 and earlier archives files uploaded for `file` parameters for Pipeline `input` steps on the controller as part of build metadata, using the parameter name without sanitization as a relative path inside a build-related directory, allowing attackers able to configure Pipelines to create or replace arbitrary files on the Jenkins controller file system with attacker-specified content.","ecosystems":["Maven","Red Hat:openshift:4.9::el8"],"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":"Arbitrary file write vulnerability in Jenkins Pipeline: Input Step Plugin","id":"CVE-2022-34177","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"path_traversal","year":"2022"},"n_packages":3,"n_references":1,"next":{"headline":"Reflected Cross site scripting in Jenkins Embeddable Build Status Plugin","id":"CVE-2022-34178"},"packages":[{"ecosystem":"Maven","fixed":["449.v77f0e8b"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:pipeline-input-step","purl":null,"source":"GHSA-29q6-p2cg-4v23"},{"ecosystem":"Maven","fixed":["449.v77f0e8b"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:pipeline-input-step","purl":"pkg:maven/org.jenkins-ci.plugins/pipeline-input-step","source":"GHSA-29q6-p2cg-4v23"},{"ecosystem":"Red Hat:openshift:4.9::el8","fixed":["0:4.9.1669894222-1.el8"],"introduced":["0"],"last_affected":[],"package":"jenkins-2-plugins","purl":"pkg:rpm/redhat/jenkins-2-plugins","source":"RHSA-2022:9110"}],"prev":{"headline":"Cross-site Scripting in Jenkins JUnit Plugin","id":"CVE-2022-34176"},"products":["Jenkins Pipeline: Input Step Plugin"],"published":"2022-06-22","related":[{"cvss_score":9.9,"headline":"Jenkins Matrix Project Plugin Remote Code Execution","id":"CVE-2019-1003030","kev_date_added":"2022-03-25","published":"2019-03-08"},{"cvss_score":9.9,"headline":"Jenkins Pipeline: Groovy Plugin allows sandbox protection bypass and arbitrary code execution","id":"CVE-2022-43402","kev_date_added":null,"published":"2022-10-19"},{"cvss_score":9.8,"headline":"Sandbox bypass vulnerability in Jenkins Pipeline: Groovy Plugin","id":"CVE-2019-1003041","kev_date_added":null,"published":"2019-03-28"},{"cvss_score":8.8,"headline":"CSRF protection for any URL can be bypassed in Jenkins Pipeline: Input Step Plugin","id":"CVE-2022-43407","kev_date_added":null,"published":"2022-10-19"},{"cvss_score":8.8,"headline":"Improper Neutralization of Special Elements used in an OS Command in Jenkins Pipeline: Groovy Plugin","id":"CVE-2022-25173","kev_date_added":null,"published":"2022-02-15"},{"cvss_score":8.8,"headline":"Improper Neutralization of Special Elements used in an OS Command in Jenkins Pipeline: Shared Groovy Libraries Plugin","id":"CVE-2022-25174","kev_date_added":null,"published":"2022-02-15"},{"cvss_score":8.8,"headline":"Jenkins Pipeline: Multibranch Plugin vulnerable to OS Command Injection","id":"CVE-2022-25175","kev_date_added":null,"published":"2022-02-15"}],"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":"CC BY 4.0","name":"Red Hat","prefix":"RHSA"},{"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 can create or replace arbitrary files on the Jenkins controller by exploiting unsanitized parameter names in Pipeline input steps.","url":"https://insights.sbomify.com/CVE-2022-34177/"}