{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:saml. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-21678 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:saml to 2.0.8 or later.","what":"CVE-2021-21678 is a high-severity vulnerability in Jenkins SAML Plugin, published on 31 Aug 2021. 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-2021-21678 and fix it if it is affected.\n\nWhat it is: CVE-2021-21678 is a high-severity vulnerability in Jenkins SAML Plugin, published on 31 Aug 2021. 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-2021-21678 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:saml (Maven): affected all versions; fixed in 2.0.8\n- org.jenkins-ci.plugins:saml (Maven): affected all versions; fixed in 2.0.8\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-2021-21678/ (Markdown: https://insights.sbomify.com/CVE-2021-21678/index.md)","id":"CVE-2021-21678","markdown":"https://insights.sbomify.com/CVE-2021-21678/index.md","name":"CVE-2021-21678","record":{"aliases":["GHSA-r5w3-pfq8-3r82"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins SAML Plugin","requires_auth":"none","summary":"Attackers can craft URLs to bypass CSRF protection in Jenkins via the SAML Plugin, potentially allowing unauthorized actions.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"saml","vendor":"jenkins"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Jenkins SAML Plugin 2.0.7 and earlier allows attackers to craft URLs that would bypass the CSRF protection of any target URL in Jenkins.","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 SAML Plugin allows bypassing CSRF protection for any URL","id":"CVE-2021-21678","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"csrf","year":"2021"},"n_packages":2,"n_references":2,"next":{"headline":"Jenkins Azure AD Plugin allows bypassing CSRF protection for any URL","id":"CVE-2021-21679"},"packages":[{"ecosystem":"Maven","fixed":["2.0.8"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:saml","purl":null,"source":"GHSA-r5w3-pfq8-3r82"},{"ecosystem":"Maven","fixed":["2.0.8"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:saml","purl":"pkg:maven/org.jenkins-ci.plugins/saml","source":"GHSA-r5w3-pfq8-3r82"}],"prev":{"headline":"RCE vulnerability in Jenkins Code Coverage API Plugin","id":"CVE-2021-21677"},"products":["Jenkins SAML Plugin"],"published":"2021-08-31","related":[{"cvss_score":7.5,"headline":"Jenkins SAML Plugin does not implement a replay cache","id":"CVE-2025-64131","kev_date_added":null,"published":"2025-10-29"},{"cvss_score":5.9,"headline":"Jenkins SAML Plugin Session Fixation vulnerability","id":"CVE-2018-1000602","kev_date_added":null,"published":"2018-06-26"}],"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-03","vendors":["Jenkins project"]},"summary":"Attackers can craft URLs to bypass CSRF protection in Jenkins via the SAML Plugin, potentially allowing unauthorized actions.","url":"https://insights.sbomify.com/CVE-2021-21678/"}