Summary
Workarounds
There are no workarounds.
References
Refer to the pull request #19810 for more information on the fix.
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.
CVE-2024-36107 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.0.0-20240527191746-e0fe7cc39172); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
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
Frequently Asked Questions
- What is CVE-2024-36107? CVE-2024-36107 is a medium-severity security vulnerability in github.com/minio/minio (go), affecting versions < 0.0.0-20240527191746-e0fe7cc39172. It is fixed in 0.0.0-20240527191746-e0fe7cc39172.
- How severe is CVE-2024-36107? CVE-2024-36107 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/minio/minio are affected by CVE-2024-36107? github.com/minio/minio (go) versions < 0.0.0-20240527191746-e0fe7cc39172 is affected.
- Is there a fix for CVE-2024-36107? Yes. CVE-2024-36107 is fixed in 0.0.0-20240527191746-e0fe7cc39172. Upgrade to this version or later.
- Is CVE-2024-36107 exploitable, and should I be worried? Whether CVE-2024-36107 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2024-36107 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2024-36107? Upgrade
github.com/minio/minioto 0.0.0-20240527191746-e0fe7cc39172 or later.