{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:naginator. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-45382 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:naginator to 1.18.2 or later.","what":"CVE-2022-45382 is a medium-severity cross-site scripting vulnerability in Jenkins Naginator Plugin, published on 15 Nov 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-45382 and fix it if it is affected.\n\nWhat it is: CVE-2022-45382 is a medium-severity cross-site scripting vulnerability in Jenkins Naginator Plugin, published on 15 Nov 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-45382 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:naginator (Maven): affected all versions; fixed in 1.18.2\n- org.jenkins-ci.plugins:naginator (Maven): affected all versions; fixed in 1.18.2\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-45382/ (Markdown: https://insights.sbomify.com/CVE-2022-45382/index.md)","id":"CVE-2022-45382","markdown":"https://insights.sbomify.com/CVE-2022-45382/index.md","name":"CVE-2022-45382","record":{"aliases":["GHSA-h8hf-hxx6-5g6v"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Naginator Plugin","requires_auth":"low_privilege","summary":"Stored XSS in Jenkins Naginator Plugin allows attackers with build name edit rights to execute scripts in victim browsers.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"naginator","vendor":"jenkins"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Jenkins Naginator Plugin 1.18.1 and earlier does not escape display names of source builds in builds that were triggered via Retry action, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to edit build display names.","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":"Cross-site Scripting in Jenkins Naginator Plugin","id":"CVE-2022-45382","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"xss","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"Incorrect permission checks in Jenkins Support Core Plugin","id":"CVE-2022-45383"},"packages":[{"ecosystem":"Maven","fixed":["1.18.2"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:naginator","purl":null,"source":"GHSA-h8hf-hxx6-5g6v"},{"ecosystem":"Maven","fixed":["1.18.2"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:naginator","purl":"pkg:maven/org.jenkins-ci.plugins/naginator","source":"GHSA-h8hf-hxx6-5g6v"}],"prev":{"headline":"Arbitrary file read vulnerability in Jenkins Pipeline Utility Steps Plugin","id":"CVE-2022-45381"},"products":["Jenkins Naginator Plugin"],"published":"2022-11-15","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-30","vendors":["Jenkins project"]},"summary":"Stored XSS in Jenkins Naginator Plugin allows attackers with build name edit rights to execute scripts in victim browsers.","url":"https://insights.sbomify.com/CVE-2022-45382/"}