{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-21362 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2021-21362 is a high-severity vulnerability in minio, published on 8 Mar 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-21362 and fix it if it is affected.\n\nWhat it is: CVE-2021-21362 is a high-severity vulnerability in minio, published on 8 Mar 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-21362 in the wild and no public exploit code.\n\nAffected product: minio. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-21362/ (Markdown: https://insights.sbomify.com/CVE-2021-21362/index.md)","id":"CVE-2021-21362","markdown":"https://insights.sbomify.com/CVE-2021-21362/index.md","name":"CVE-2021-21362","record":{"aliases":["GHSA-hq5j-6r98-9m8v","MINI-8q66-wv8v-5pww","MINI-fgpm-38vg-2j6g"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MinIO object storage","requires_auth":"low_privilege","summary":"Attackers can bypass read-only policies in MinIO by generating temporary upload URLs, allowing unauthorized data modification.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"minio","vendor":"minio"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-285","name":"Improper Authorization"}],"description":"MinIO is an open-source high performance object storage service and it is API compatible with Amazon S3 cloud storage service. In MinIO before version RELEASE.2021-03-04T00-53-13Z it is possible to bypass a readOnly policy by creating a temporary 'mc share upload' URL. Everyone is impacted who uses MinIO multi-users. This is fixed in version RELEASE.2021-03-04T00-53-13Z. As a workaround, one can disable uploads with `Content-Type: multipart/form-data` as mentioned in the S3 API RESTObjectPOST docs by using a proxy in front of MinIO.","ecosystems":[],"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":"Bypassing readOnly policy by creating a temporary 'mc share upload' URL","id":"CVE-2021-21362","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2021"},"n_packages":0,"n_references":4,"next":{"headline":"Generator Web Application: Local Privilege Escalation Vulnerability via System Temp Directory","id":"CVE-2021-21363"},"packages":[],"prev":{"headline":"Sensitive information disclosure via log in com.bmuschko:gradle-vagrant-plugin","id":"CVE-2021-21361"},"products":["minio"],"published":"2021-03-08","related":[{"cvss_score":8.8,"headline":"MinIO Security Feature Bypass","id":"CVE-2023-28434","kev_date_added":"2023-09-19","published":"2023-03-22"},{"cvss_score":7.5,"headline":"MinIO Information Disclosure","id":"CVE-2023-28432","kev_date_added":"2023-04-21","published":"2023-03-22"},{"cvss_score":9.3,"headline":"Authentication bypass MinIO Admin API","id":"CVE-2020-11012","kev_date_added":null,"published":"2020-04-23"},{"cvss_score":9.2,"headline":"MinIO: JWT Algorithm Confusion in OIDC Authentication","id":"CVE-2026-33322","kev_date_added":null,"published":"2026-03-24"},{"cvss_score":9.1,"headline":"MinIO: LDAP login brute-force via user enumeration and missing rate limit","id":"CVE-2026-33419","kev_date_added":null,"published":"2026-03-24"},{"cvss_score":8.8,"headline":"MinIO has an Unauthenticated Object Write via Missing Signature Verification in Unsigned-Trailer Uploads","id":"CVE-2026-40344","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":8.8,"headline":"MinIO has an Unauthenticated Object Write via Query-String Credential Signature Bypass in Unsigned-Trailer Uploads","id":"CVE-2026-41145","kev_date_added":null,"published":"2026-04-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":["minio"]},"summary":"Attackers can bypass read-only policies in MinIO by generating temporary upload URLs, allowing unauthorized data modification.","url":"https://insights.sbomify.com/CVE-2021-21362/"}