{"answers":{"affected":"4 open source packages ship an affected version, including org.jenkins-ci.plugins:s3. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-21650 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:s3 to a fixed version for your release line: 0.11.5.1 or 0.11.7.","what":"CVE-2021-21650 is a medium-severity missing authorization vulnerability in Jenkins S3 publisher Plugin, published on 11 May 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-21650 and fix it if it is affected.\n\nWhat it is: CVE-2021-21650 is a medium-severity missing authorization vulnerability in Jenkins S3 publisher Plugin, published on 11 May 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-21650 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:s3 (Maven): affected all versions; fixed in 0.11.5.1\n- org.jenkins-ci.plugins:s3 (Maven): affected all versions; fixed in 0.11.5.1\n- org.jenkins-ci.plugins:s3 (Maven): affected from 0.11.6; fixed in 0.11.7\n- org.jenkins-ci.plugins:s3 (Maven): affected from 0.11.6; fixed in 0.11.7\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-21650/ (Markdown: https://insights.sbomify.com/CVE-2021-21650/index.md)","id":"CVE-2021-21650","markdown":"https://insights.sbomify.com/CVE-2021-21650/index.md","name":"CVE-2021-21650","record":{"aliases":["GHSA-fvfc-8pqr-wjpv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Jenkins S3 plugin","requires_auth":"low_privilege","summary":"Attackers with read permissions can access S3 artifact information due to missing authorization checks in the Jenkins S3 publisher plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"s3_publisher","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:L/I:N/A:N","version":"3.1"},"cwes":[],"description":"Jenkins S3 publisher Plugin 0.11.6 and earlier does not perform Run/Artifacts permission checks in various HTTP endpoints and API models, allowing attackers with Item/Read permission to obtain information about artifacts uploaded to S3, if the optional Run/Artifacts permission is enabled.","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":"Missing Authorization in Jenkins S3 publisher Plugin","id":"CVE-2021-21650","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"missing_authorization","year":"2021"},"n_packages":4,"n_references":1,"next":{"headline":"Missing Authorization in Jenkins S3 publisher Plugin","id":"CVE-2021-21651"},"packages":[{"ecosystem":"Maven","fixed":["0.11.5.1"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:s3","purl":null,"source":"GHSA-fvfc-8pqr-wjpv"},{"ecosystem":"Maven","fixed":["0.11.5.1"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:s3","purl":"pkg:maven/org.jenkins-ci.plugins/s3","source":"GHSA-fvfc-8pqr-wjpv"},{"ecosystem":"Maven","fixed":["0.11.7"],"introduced":["0.11.6"],"last_affected":[],"package":"org.jenkins-ci.plugins:s3","purl":null,"source":"GHSA-fvfc-8pqr-wjpv"},{"ecosystem":"Maven","fixed":["0.11.7"],"introduced":["0.11.6"],"last_affected":[],"package":"org.jenkins-ci.plugins:s3","purl":"pkg:maven/org.jenkins-ci.plugins/s3","source":"GHSA-fvfc-8pqr-wjpv"}],"prev":{"headline":"Cross-site Scripting in Jenkins Dashboard View Plugin","id":"CVE-2021-21649"},"products":["Jenkins S3 publisher Plugin"],"published":"2021-05-11","related":[{"cvss_score":7.5,"headline":"Jenkins S3 Publisher Plugin transmits credentials in plain text during configuration","id":"CVE-2020-2114","kev_date_added":null,"published":"2020-02-12"},{"cvss_score":5.4,"headline":"Stored XSS vulnerability in Jenkins S3 Publisher Plugin","id":"CVE-2018-1000177","kev_date_added":null,"published":"2018-05-08"},{"cvss_score":4.3,"headline":"Missing Authorization in Jenkins S3 publisher Plugin","id":"CVE-2021-21651","kev_date_added":null,"published":"2021-05-11"}],"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":"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 read permissions can access S3 artifact information due to missing authorization checks in the Jenkins S3 publisher plugin.","url":"https://insights.sbomify.com/CVE-2021-21650/"}