{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:release. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1000013 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:release to 2.10 or later.","what":"CVE-2018-1000013 is a high-severity vulnerability in n/a, published on 23 Jan 2018. 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-2018-1000013 and fix it if it is affected.\n\nWhat it is: CVE-2018-1000013 is a high-severity vulnerability in n/a, published on 23 Jan 2018. 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-2018-1000013 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:release (Maven): affected all versions; fixed in 2.10\n- org.jenkins-ci.plugins:release (Maven): affected all versions; fixed in 2.10\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-2018-1000013/ (Markdown: https://insights.sbomify.com/CVE-2018-1000013/index.md)","id":"CVE-2018-1000013","markdown":"https://insights.sbomify.com/CVE-2018-1000013/index.md","name":"CVE-2018-1000013","record":{"aliases":["GHSA-j2h6-j34w-g5vp"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Release Plugin","requires_auth":"none","summary":"Attackers can trigger unauthorized release builds in Jenkins via CSRF due to missing POST method enforcement in the Release Plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"release","vendor":"jenkins"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Jenkins Release Plugin 2.9 and earlier did not require form submissions to be submitted via POST, resulting in a CSRF vulnerability allowing attackers to trigger release builds.","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":"CSRF vulnerability in Jenkins Release plugin","id":"CVE-2018-1000013","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"csrf","year":"2018"},"n_packages":2,"n_references":2,"next":{"headline":"CSRF vulnerability in Jenkins Translation Assistance plugin","id":"CVE-2018-1000014"},"packages":[{"ecosystem":"Maven","fixed":["2.10"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:release","purl":null,"source":"GHSA-j2h6-j34w-g5vp"},{"ecosystem":"Maven","fixed":["2.10"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:release","purl":"pkg:maven/org.jenkins-ci.plugins/release","source":"GHSA-j2h6-j34w-g5vp"}],"prev":{"headline":"XXE vulnerability Jenkins Warnings Plugin","id":"CVE-2018-1000012"},"products":["n/a"],"published":"2018-01-23","related":[{"cvss_score":5.4,"headline":"Stored XSS vulnerability in Jenkins Release Plugin","id":"CVE-2020-2292","kev_date_added":null,"published":"2020-10-08"}],"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-05","vendors":["n/a"]},"summary":"Attackers can trigger unauthorized release builds in Jenkins via CSRF due to missing POST method enforcement in the Release Plugin.","url":"https://insights.sbomify.com/CVE-2018-1000013/"}