{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:selenium. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-2196 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-2196 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-2196 is a high-severity vulnerability in Jenkins Selenium Plugin, published on 3 Jun 2020. 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-2020-2196 and fix it if it is affected.\n\nWhat it is: CVE-2020-2196 is a high-severity vulnerability in Jenkins Selenium Plugin, published on 3 Jun 2020. 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-2020-2196 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:selenium (Maven): affected all versions up to 3.141.59; no fix listed\n- org.jenkins-ci.plugins:selenium (Maven): affected all versions up to 3.141.59; 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-2020-2196/ (Markdown: https://insights.sbomify.com/CVE-2020-2196/index.md)","id":"CVE-2020-2196","markdown":"https://insights.sbomify.com/CVE-2020-2196/index.md","name":"CVE-2020-2196","record":{"aliases":["GHSA-rp4x-xpgf-4xv7"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Selenium Plugin","requires_auth":"low_privilege","summary":"Attackers can perform administrative actions on the Jenkins Selenium Plugin due to missing CSRF protection, requiring an upgrade to secure the endpoints.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"selenium","vendor":"jenkins"}],"cvss":{"score":8,"severity":"high","source":"nvd","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":"Jenkins Selenium Plugin 3.141.59 and earlier has no CSRF protection for its HTTP endpoints, allowing attackers to perform all administrative actions provided by the plugin.","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":"Complete lack of CSRF protection in Jenkins Selenium Plugin can lead to OS command injection","id":"CVE-2020-2196","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"csrf","year":"2020"},"n_packages":2,"n_references":3,"next":{"headline":"Missing permission check in Jenkins Project Inheritance Plugin","id":"CVE-2020-2197"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["3.141.59"],"package":"org.jenkins-ci.plugins:selenium","purl":null,"source":"GHSA-rp4x-xpgf-4xv7"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["3.141.59"],"package":"org.jenkins-ci.plugins:selenium","purl":"pkg:maven/org.jenkins-ci.plugins/selenium","source":"GHSA-rp4x-xpgf-4xv7"}],"prev":{"headline":"Stored XSS vulnerability in Jenkins Compact Columns Plugin","id":"CVE-2020-2195"},"products":["Jenkins Selenium Plugin"],"published":"2020-06-03","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Jenkins project"]},"summary":"Attackers can perform administrative actions on the Jenkins Selenium Plugin due to missing CSRF protection, requiring an upgrade to secure the endpoints.","url":"https://insights.sbomify.com/CVE-2020-2196/"}