{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:junit. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1000411 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:junit to 1.26 or later.","what":"CVE-2018-1000411 is a medium-severity vulnerability in n/a, published on 9 Jan 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-2018-1000411 and fix it if it is affected.\n\nWhat it is: CVE-2018-1000411 is a medium-severity vulnerability in n/a, published on 9 Jan 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-2018-1000411 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:junit (Maven): affected all versions; fixed in 1.26\n- org.jenkins-ci.plugins:junit (Maven): affected all versions; fixed in 1.26\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-1000411/ (Markdown: https://insights.sbomify.com/CVE-2018-1000411/index.md)","id":"CVE-2018-1000411","markdown":"https://insights.sbomify.com/CVE-2018-1000411/index.md","name":"CVE-2018-1000411","record":{"aliases":["GHSA-x9gm-m8pp-54vx"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins JUnit Plugin","requires_auth":"none","summary":"Attackers can force users to modify test result descriptions via CSRF, requiring plugin updates to mitigate.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"junit","vendor":"jenkins"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"A cross-site request forgery vulnerability exists in Jenkins JUnit Plugin 1.25 and earlier in TestObject.java that allows setting the description of a test result.","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 JUnit Plugin CSRF vulnerability","id":"CVE-2018-1000411","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"csrf","year":"2018"},"n_packages":2,"n_references":2,"next":{"headline":"Jenkins Jira Plugin Incorrect Authorization vulnerability","id":"CVE-2018-1000412"},"packages":[{"ecosystem":"Maven","fixed":["1.26"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:junit","purl":null,"source":"GHSA-x9gm-m8pp-54vx"},{"ecosystem":"Maven","fixed":["1.26"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:junit","purl":"pkg:maven/org.jenkins-ci.plugins/junit","source":"GHSA-x9gm-m8pp-54vx"}],"prev":{"headline":"Exposure of Sensitive Information to an Unauthorized Actor in Jenkins","id":"CVE-2018-1000410"},"products":["n/a"],"published":"2019-01-09","related":[{"cvss_score":8.3,"headline":"Improper Restriction of XML External Entity Reference in Jenkins JUnit Plugin","id":"CVE-2018-1000056","kev_date_added":null,"published":"2018-02-09"},{"cvss_score":5.4,"headline":"Cross-site Scripting in Jenkins JUnit Plugin","id":"CVE-2023-25761","kev_date_added":null,"published":"2023-02-15"},{"cvss_score":5.4,"headline":"Jenkins JUnit Plugin subject to Cross-site Scripting via URL conversion","id":"CVE-2022-45380","kev_date_added":null,"published":"2022-11-15"},{"cvss_score":5.4,"headline":"Cross-site Scripting in Jenkins JUnit Plugin","id":"CVE-2022-34176","kev_date_added":null,"published":"2022-06-22"}],"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 force users to modify test result descriptions via CSRF, requiring plugin updates to mitigate.","url":"https://insights.sbomify.com/CVE-2018-1000411/"}