{"answers":{"affected":"3 open source packages ship an affected version, including github.com/minio/minio.","exploited":"There is no known exploitation of CVE-2024-36107 in the wild and no public exploit code.","fix":"Upgrade github.com/minio/minio to 0.0.0-20240527191746-e0fe7cc39172 or later.","what":"CVE-2024-36107 is a medium-severity vulnerability in minio, published on 28 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-36107 and fix it if it is affected.\n\nWhat it is: CVE-2024-36107 is a medium-severity vulnerability in minio, published on 28 May 2024. 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-2024-36107 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/minio/minio (Go): affected all versions; fixed in 0.0.0-20240527191746-e0fe7cc39172\n- github.com/minio/minio (Go): affected all versions; fixed in 0.0.0-20240527191746-e0fe7cc39172\n- github.com/minio/minio (Go): affected all versions; fixed in 0.0.0-20240527191746-e0fe7cc39172\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-2024-36107/ (Markdown: https://insights.sbomify.com/CVE-2024-36107/index.md)","id":"CVE-2024-36107","markdown":"https://insights.sbomify.com/CVE-2024-36107/index.md","name":"CVE-2024-36107","record":{"aliases":["GHSA-95fr-cm4m-q5p9","GO-2024-2886"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"MinIO object storage","requires_auth":"none","summary":"Anonymous users can determine object existence and retrieve metadata via conditional headers, requiring an upgrade to MinIO.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","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":"MinIO is a High Performance Object Storage released under GNU Affero General Public License v3.0. `If-Modified-Since` and `If-Unmodified-Since` headers when used with anonymous requests by sending a random object name requests can be used to determine if an object exists or not on the server on a specific bucket and also gain access to some amount of\ninformation such as  `Last-Modified (of the latest version)`, `Etag (of the latest version)`, `x-amz-version-id (of the latest version)`, `Expires (metadata value of the latest version)`, `Cache-Control (metadata value of the latest version)`. This conditional check was being honored before validating if the anonymous access is indeed allowed on the metadata of an object. This issue has been addressed in commit `e0fe7cc3917`. Users must upgrade to RELEASE.2024-05-27T19-17-46Z for the fix. There are no known workarounds for this issue.","ecosystems":["Go"],"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":"Information disclosure in minio","id":"CVE-2024-36107","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":3,"n_references":5,"next":{"headline":"Multiple Broken Function-Level Authorization vulnerabilities in casgate","id":"CVE-2024-36108"},"packages":[{"ecosystem":"Go","fixed":["0.0.0-20240527191746-e0fe7cc39172"],"introduced":["0"],"last_affected":[],"package":"github.com/minio/minio","purl":null,"source":"GHSA-95fr-cm4m-q5p9"},{"ecosystem":"Go","fixed":["0.0.0-20240527191746-e0fe7cc39172"],"introduced":["0"],"last_affected":[],"package":"github.com/minio/minio","purl":"pkg:golang/github.com/minio/minio","source":"GHSA-95fr-cm4m-q5p9"},{"ecosystem":"Go","fixed":["0.0.0-20240527191746-e0fe7cc39172"],"introduced":["0"],"last_affected":[],"package":"github.com/minio/minio","purl":"pkg:golang/github.com/minio/minio","source":"GO-2024-2886"}],"prev":{"headline":"Argo CD allows authenticated users to enumerate clusters by name","id":"CVE-2024-36106"},"products":["minio"],"published":"2024-05-28","related":[],"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":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-03","vendors":["minio"]},"summary":"Anonymous users can determine object existence and retrieve metadata via conditional headers, requiring an upgrade to MinIO.","url":"https://insights.sbomify.com/CVE-2024-36107/"}