{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:parameterized-trigger. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-27195 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:parameterized-trigger to 2.43.1 or later.","what":"CVE-2022-27195 is a medium-severity vulnerability in Jenkins Parameterized Trigger Plugin, published on 15 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-27195 and fix it if it is affected.\n\nWhat it is: CVE-2022-27195 is a medium-severity vulnerability in Jenkins Parameterized Trigger Plugin, published on 15 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-27195 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:parameterized-trigger (Maven): affected all versions; fixed in 2.43.1\n- org.jenkins-ci.plugins:parameterized-trigger (Maven): affected all versions; fixed in 2.43.1\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-27195/ (Markdown: https://insights.sbomify.com/CVE-2022-27195/index.md)","id":"CVE-2022-27195","markdown":"https://insights.sbomify.com/CVE-2022-27195/index.md","name":"CVE-2022-27195","record":{"aliases":["GHSA-5mpf-hw8f-86w9"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Jenkins plugin","requires_auth":"low_privilege","summary":"Attackers with file system access can read unencrypted passwords from build logs in the Jenkins Parameterized Trigger Plugin.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"parameterized_trigger","vendor":"jenkins"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"Jenkins Parameterized Trigger Plugin 2.43 and earlier captures environment variables passed to builds triggered using Jenkins Parameterized Trigger Plugin, including password parameter values, in their `build.xml` files. These values are stored unencrypted and can be viewed by users with access to 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":"Sensitive parameter values captured in build metadata files by Jenkins Parameterized Trigger Plugin","id":"CVE-2022-27195","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"Stored Cross-site Scripting vulnerability in Jenkins Favorite Plugin","id":"CVE-2022-27196"},"packages":[{"ecosystem":"Maven","fixed":["2.43.1"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:parameterized-trigger","purl":null,"source":"GHSA-5mpf-hw8f-86w9"},{"ecosystem":"Maven","fixed":["2.43.1"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:parameterized-trigger","purl":"pkg:maven/org.jenkins-ci.plugins/parameterized-trigger","source":"GHSA-5mpf-hw8f-86w9"}],"prev":{"headline":"Denial of service in SIMATIC PCS neo (Administration Console)","id":"CVE-2022-27194"},"products":["Jenkins Parameterized Trigger Plugin"],"published":"2022-03-15","related":[{"cvss_score":6.5,"headline":"Parameterized Trigger Plugin fails to check Item/Build permission","id":"CVE-2017-1000084","kev_date_added":null,"published":"2017-10-04"}],"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":"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 file system access can read unencrypted passwords from build logs in the Jenkins Parameterized Trigger Plugin.","url":"https://insights.sbomify.com/CVE-2022-27195/"}