# CVE-2024-36107: Information disclosure in minio

> Anonymous users can determine object existence and retrieve metadata via conditional headers, requiring an upgrade to MinIO.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2024
- **Updated:** 3 Sep 2024
- **Also known as:** GHSA-95fr-cm4m-q5p9, GO-2024-2886

## What is CVE-2024-36107?

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.

### Official 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
information 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-36107?

3 open source packages ship an affected version, including github.com/minio/minio.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/minio/minio` | Go | All versions | 0.0.0-20240527191746-e0fe7cc39172 |
| `github.com/minio/minio` | Go | All versions | 0.0.0-20240527191746-e0fe7cc39172 |
| `github.com/minio/minio` | Go | All versions | 0.0.0-20240527191746-e0fe7cc39172 |

## How do I fix CVE-2024-36107?

Upgrade github.com/minio/minio to 0.0.0-20240527191746-e0fe7cc39172 or later.

## Is CVE-2024-36107 being exploited?

There is no known exploitation of CVE-2024-36107 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36107 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2024-36107 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/minio/minio (Go): affected all versions; fixed in 0.0.0-20240527191746-e0fe7cc39172
- github.com/minio/minio (Go): affected all versions; fixed in 0.0.0-20240527191746-e0fe7cc39172
- github.com/minio/minio (Go): affected all versions; fixed in 0.0.0-20240527191746-e0fe7cc39172

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-36107/ (Markdown: https://insights.sbomify.com/CVE-2024-36107/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-36107
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-36107
- OSV: https://osv.dev/vulnerability/CVE-2024-36107

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-36107/
Summaries are generated and may contain mistakes; the official description above is the record.