{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins.m2release:m2release. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10359 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins.m2release:m2release to 0.15.0 or later.","what":"CVE-2019-10359 is a medium-severity vulnerability in Jenkins Maven Release Plugin, published on 31 Jul 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-10359 and fix it if it is affected.\n\nWhat it is: CVE-2019-10359 is a medium-severity vulnerability in Jenkins Maven Release Plugin, published on 31 Jul 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-10359 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins.m2release:m2release (Maven): affected all versions; fixed in 0.15.0\n- org.jenkins-ci.plugins.m2release:m2release (Maven): affected all versions; fixed in 0.15.0\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-2019-10359/ (Markdown: https://insights.sbomify.com/CVE-2019-10359/index.md)","id":"CVE-2019-10359","markdown":"https://insights.sbomify.com/CVE-2019-10359/index.md","name":"CVE-2019-10359","record":{"aliases":["GHSA-r4rv-cq77-6p24"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Maven Release Plugin","requires_auth":"none","summary":"Attackers can force Jenkins users to perform Maven releases with malicious options via cross-site request forgery.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"m2release","vendor":"jenkins"}],"cvss":{"score":6.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"A cross-site request forgery vulnerability in Jenkins Maven Release Plugin 0.14.0 and earlier in the M2ReleaseAction#doSubmit method allowed attackers to perform releases with attacker-specified options.","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 Maven Release Plugin contains Cross-Site Request Forgery vulnerability","id":"CVE-2019-10359","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"csrf","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"Jenkins Maven Release Plugin vulnerable to Cross-site Scripting","id":"CVE-2019-10360"},"packages":[{"ecosystem":"Maven","fixed":["0.15.0"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins.m2release:m2release","purl":null,"source":"GHSA-r4rv-cq77-6p24"},{"ecosystem":"Maven","fixed":["0.15.0"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins.m2release:m2release","purl":"pkg:maven/org.jenkins-ci.plugins.m2release/m2release","source":"GHSA-r4rv-cq77-6p24"}],"prev":{"headline":"Maven Integration Plugin did not mask sensitive values in module build logs","id":"CVE-2019-10358"},"products":["Jenkins Maven Release Plugin"],"published":"2019-07-31","related":[{"cvss_score":5.5,"headline":"Jenkins Maven Release Plug-in Plugin stored credentials in plain text","id":"CVE-2019-10361","kev_date_added":null,"published":"2019-07-31"}],"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-04","vendors":["Jenkins project"]},"summary":"Attackers can force Jenkins users to perform Maven releases with malicious options via cross-site request forgery.","url":"https://insights.sbomify.com/CVE-2019-10359/"}