{"answers":{"affected":"5 open source packages ship an affected version, including org.jenkins-ci.main:jenkins-core and jenkins. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-21640 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.main:jenkins-core to a fixed version for your release line: 2.277.2 or 2.287.","what":"CVE-2021-21640 is a medium-severity vulnerability in Jenkins Jenkins, published on 7 Apr 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-21640 and fix it if it is affected.\n\nWhat it is: CVE-2021-21640 is a medium-severity vulnerability in Jenkins Jenkins, published on 7 Apr 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-21640 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.main:jenkins-core (Maven): affected all versions; fixed in 2.277.2\n- org.jenkins-ci.main:jenkins-core (Maven): affected all versions; fixed in 2.277.2\n- org.jenkins-ci.main:jenkins-core (Maven): affected from 2.278; fixed in 2.287\n- org.jenkins-ci.main:jenkins-core (Maven): affected from 2.278; fixed in 2.287\n- jenkins (Bitnami): affected all versions; fixed in 2.286.1\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-21640/ (Markdown: https://insights.sbomify.com/CVE-2021-21640/index.md)","id":"CVE-2021-21640","markdown":"https://insights.sbomify.com/CVE-2021-21640/index.md","name":"CVE-2021-21640","record":{"aliases":["BIT-jenkins-2021-21640","GHSA-w2hv-rcqr-2h7r"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins CI server","requires_auth":"low_privilege","summary":"Attackers with view creation permissions can create views with invalid or duplicate names, bypassing validation logic in Jenkins.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"jenkins","vendor":"jenkins"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[],"description":"Jenkins 2.286 and earlier, LTS 2.277.1 and earlier does not properly check that a newly created view has an allowed name, allowing attackers with View/Create permission to create views with invalid or already-used names.","ecosystems":["Bitnami","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":"View name validation bypass in Jenkins","id":"CVE-2021-21640","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"jenkins:jenkins","products":["jenkins:jenkins"],"type":"business_logic","year":"2021"},"n_packages":5,"n_references":2,"next":{"headline":"CSRF vulnerability in Jenkins promoted builds Plugin","id":"CVE-2021-21641"},"packages":[{"ecosystem":"Bitnami","fixed":["2.286.1"],"introduced":["0"],"last_affected":[],"package":"jenkins","purl":"pkg:bitnami/jenkins","source":"BIT-jenkins-2021-21640"},{"ecosystem":"Maven","fixed":["2.277.2"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.main:jenkins-core","purl":null,"source":"GHSA-w2hv-rcqr-2h7r"},{"ecosystem":"Maven","fixed":["2.277.2"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.main:jenkins-core","purl":"pkg:maven/org.jenkins-ci.main/jenkins-core","source":"GHSA-w2hv-rcqr-2h7r"},{"ecosystem":"Maven","fixed":["2.287"],"introduced":["2.278"],"last_affected":[],"package":"org.jenkins-ci.main:jenkins-core","purl":null,"source":"GHSA-w2hv-rcqr-2h7r"},{"ecosystem":"Maven","fixed":["2.287"],"introduced":["2.278"],"last_affected":[],"package":"org.jenkins-ci.main:jenkins-core","purl":"pkg:maven/org.jenkins-ci.main/jenkins-core","source":"GHSA-w2hv-rcqr-2h7r"}],"prev":{"headline":"Lack of type validation in agent related REST API in Jenkins","id":"CVE-2021-21639"},"products":["Jenkins"],"published":"2021-04-07","related":[{"cvss_score":9.8,"headline":"Jenkins Command Line Interface (CLI) Path Traversal","id":"CVE-2024-23897","kev_date_added":"2024-08-19","published":"2024-01-24"},{"cvss_score":9.8,"headline":"Jenkins Stapler Web Framework Deserialization of Untrusted Data","id":"CVE-2018-1000861","kev_date_added":"2022-02-10","published":"2018-12-10"},{"cvss_score":9.8,"headline":"Jenkins Remote Code Execution","id":"CVE-2017-1000353","kev_date_added":"2025-10-02","published":"2018-01-29"},{"cvss_score":7.5,"headline":"Jenkins User Interface (UI) Information Disclosure","id":"CVE-2015-5317","kev_date_added":"2023-05-12","published":"2015-11-25"},{"cvss_score":9.8,"headline":"Multiple vulnerabilities allow bypassing path filtering of agent-to-controller access control in Jenkins","id":"CVE-2021-21690","kev_date_added":null,"published":"2021-11-04"},{"cvss_score":9.8,"headline":"Multiple vulnerabilities allow bypassing path filtering of agent-to-controller access control in Jenkins","id":"CVE-2021-21691","kev_date_added":null,"published":"2021-11-04"},{"cvss_score":9.8,"headline":"Multiple vulnerabilities allow bypassing path filtering of agent-to-controller access control in Jenkins","id":"CVE-2021-21692","kev_date_added":null,"published":"2021-11-04"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":"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 with view creation permissions can create views with invalid or duplicate names, bypassing validation logic in Jenkins.","url":"https://insights.sbomify.com/CVE-2021-21640/"}