{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:build-publisher. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-41232 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-41232 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-41232 is a high-severity vulnerability in Jenkins Build-Publisher Plugin, published on 21 Sep 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-41232 and fix it if it is affected.\n\nWhat it is: CVE-2022-41232 is a high-severity vulnerability in Jenkins Build-Publisher Plugin, published on 21 Sep 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-41232 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:build-publisher (Maven): affected all versions up to 1.22; no fix listed\n- org.jenkins-ci.plugins:build-publisher (Maven): affected all versions up to 1.22; no fix listed\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-41232/ (Markdown: https://insights.sbomify.com/CVE-2022-41232/index.md)","id":"CVE-2022-41232","markdown":"https://insights.sbomify.com/CVE-2022-41232/index.md","name":"CVE-2022-41232","record":{"aliases":["GHSA-phr4-94xx-259m"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Build-Publisher Plugin","requires_auth":"low_privilege","summary":"Attackers can exploit CSRF to replace Jenkins controller configuration files with empty files, potentially disrupting operations.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"build-publisher","vendor":"jenkins"}],"cvss":{"score":8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"A cross-site request forgery (CSRF) vulnerability in Jenkins Build-Publisher Plugin 1.22 and earlier allows attackers to replace any config.xml file on the Jenkins controller file system with an empty file by providing a crafted file name to an API endpoint.","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":false,"headline":"Jenkins build-publisher plugin vulnerable to cross-site request forgery","id":"CVE-2022-41232","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"csrf","year":"2022"},"n_packages":2,"n_references":1,"next":{"headline":"Jenkins Rundeck Plugin Missing Authorization vulnerability","id":"CVE-2022-41233"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.22"],"package":"org.jenkins-ci.plugins:build-publisher","purl":null,"source":"GHSA-phr4-94xx-259m"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.22"],"package":"org.jenkins-ci.plugins:build-publisher","purl":"pkg:maven/org.jenkins-ci.plugins/build-publisher","source":"GHSA-phr4-94xx-259m"}],"prev":{"headline":"Path traversal in Jenkins build-publisher Plugin","id":"CVE-2022-41231"},"products":["Jenkins Build-Publisher Plugin"],"published":"2022-09-21","related":[{"cvss_score":7.8,"headline":"Jenkins Build-Publisher plugin has Insufficiently Protected Credentials","id":"CVE-2017-1000387","kev_date_added":null,"published":"2018-01-26"},{"cvss_score":5.7,"headline":"Path traversal in Jenkins build-publisher Plugin","id":"CVE-2022-41231","kev_date_added":null,"published":"2022-09-21"},{"cvss_score":4.3,"headline":"Missing permission check in Jenkins build-publisher Plugin","id":"CVE-2022-41230","kev_date_added":null,"published":"2022-09-21"}],"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":"total"},"state":"PUBLISHED","updated":"2025-05-28","vendors":["Jenkins project"]},"summary":"Attackers can exploit CSRF to replace Jenkins controller configuration files with empty files, potentially disrupting operations.","url":"https://insights.sbomify.com/CVE-2022-41232/"}