{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:support-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-21621 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:support-core to 2.72.1 or later.","what":"CVE-2021-21621 is a medium-severity vulnerability in Jenkins Support Core Plugin, published on 24 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-21621 and fix it if it is affected.\n\nWhat it is: CVE-2021-21621 is a medium-severity vulnerability in Jenkins Support Core Plugin, published on 24 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-21621 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:support-core (Maven): affected all versions; fixed in 2.72.1\n- org.jenkins-ci.plugins:support-core (Maven): affected all versions; fixed in 2.72.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-21621/ (Markdown: https://insights.sbomify.com/CVE-2021-21621/index.md)","id":"CVE-2021-21621","markdown":"https://insights.sbomify.com/CVE-2021-21621/index.md","name":"CVE-2021-21621","record":{"aliases":["GHSA-92pg-8g57-hqpx"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Jenkins Support Plugin","requires_auth":"none","summary":"The Jenkins Support Core Plugin may leak session IDs in support bundles, potentially allowing attackers to hijack user accounts.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"support_core","vendor":"jenkins"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Jenkins Support Core Plugin 2.72 and earlier provides the serialized user authentication as part of the \"About user (basic authentication details only)\" information, which can include the session ID of the user creating the support bundle in some configurations.","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":"Support bundles can include user session IDs in Jenkins Support Core Plugin","id":"CVE-2021-21621","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":2,"n_references":1,"next":{"headline":"Stored XSS vulnerability in Jenkins Artifact Repository Parameter Plugin","id":"CVE-2021-21622"},"packages":[{"ecosystem":"Maven","fixed":["2.72.1"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:support-core","purl":null,"source":"GHSA-92pg-8g57-hqpx"},{"ecosystem":"Maven","fixed":["2.72.1"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:support-core","purl":"pkg:maven/org.jenkins-ci.plugins/support-core","source":"GHSA-92pg-8g57-hqpx"}],"prev":{"headline":"Cross-Site Request Forgery in the Jenkins Claim plugin","id":"CVE-2021-21620"},"products":["Jenkins Support Core Plugin"],"published":"2021-02-24","related":[{"cvss_score":6.5,"headline":"Incorrect permission checks in Jenkins Support Core Plugin","id":"CVE-2022-45383","kev_date_added":null,"published":"2022-11-15"},{"cvss_score":6.5,"headline":"Jenkins Support Core Plugin stores sensitive data in plain text","id":"CVE-2022-25187","kev_date_added":null,"published":"2022-02-15"},{"cvss_score":6.5,"headline":"Missing permission check in Jenkins Support Core Plugin","id":"CVE-2019-16539","kev_date_added":null,"published":"2019-11-21"},{"cvss_score":6.5,"headline":"Jenkins Support Core Plugin allowed users with Overall/Read permission to delete arbitrary files","id":"CVE-2019-16540","kev_date_added":null,"published":"2019-11-21"}],"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":"The Jenkins Support Core Plugin may leak session IDs in support bundles, potentially allowing attackers to hijack user accounts.","url":"https://insights.sbomify.com/CVE-2021-21621/"}