CVE-2024-36107: MinIO information disclosure vulnerability
Impact If-Modified-Since If-Unmodified-Since Headers when used with anonymous requests by sending a random object name requests you can figure out if the object exists or not on the server on a specific bucket and also gain access to some amount of information such as This conditional check was being honored before validating if the anonymous access is indeed allowed on the metadata of an object.
Published May 29, 2024
Affected packages
github.com/minio/minio
- Ecosystem
- Go
- Affected
- < 0.0.0-20240527191746-e0fe7cc39172
- Fixed in
- 0.0.0-20240527191746-e0fe7cc39172
- Check
go list -m github.com/minio/minio
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
If-Modified-Since If-Unmodified-Since
Headers when used with anonymous requests by sending a random object name requests you can figure out if the 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.
Patches
Yes this issue has been already fixed in
commit e0fe7cc391724fc5baa85b45508f425020fe4272 (HEAD -> master, origin/master)
Author: Harshavardhana <[email protected]>
Date: Mon May 27 12:17:46 2024 -0700
fix: information disclosure bug in preconditions GET (#19810)
precondition check was being honored before, validating
if anonymous access is allowed on the metadata of an
object, leading to metadata disclosure of the following
headers.
Last-Modified Etag x-amz-version-id Expires: Cache-Control:
although the information presented is minimal in nature,
and of opaque nature. It still simply discloses that an
object by a specific name exists or not without even having
enough permissions.Users must upgrade to RELEASE.2024-05-27T19-17-46Z for the fix
Workarounds
There are no workarounds.
References
Refer to the pull request #19810 for more information on the fix.
Credited to stefansundin, shtripat.
References
- https://github.com/minio/minio/security/advisories/GHSA-95fr-cm4m-q5p9
- https://nvd.nist.gov/vuln/detail/CVE-2024-36107
- https://github.com/minio/minio/pull/19810
- https://github.com/minio/minio/commit/e0fe7cc391724fc5baa85b45508f425020fe4272
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/If-Modified-Since
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/If-Unmodified-Since
- https://github.com/advisories/GHSA-95fr-cm4m-q5p9
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-42600
MinIO vulnerable to Path Traversal via msgpack Body in `ReadMultiple` Storage-REST Endpoint
medium4.9May 5, 2026CVE-2026-40344
MinIO has an Unauthenticated Object Write via Missing Signature Verification in Unsigned-Trailer Uploads
high8.2No fixApr 14, 2026CVE-2026-41145
MinIO has an Unauthenticated Object Write via Query-String Credential Signature Bypass in Unsigned-Trailer Uploads
high8.2No fixApr 14, 2026CVE-2026-39414
MinIO affected a DoS via Unbounded Memory Allocation in S3 Select CSV Parsing
high7.1No fixApr 9, 2026CVE-2026-34204
MinIO is Vulnerable to SSE Metadata Injection via Replication Headers
high7.1No fixMar 27, 2026CVE-2026-33419
MinIO LDAP login brute-force via user enumeration and missing rate limit
critical9.1No fixMar 20, 2026
