Skip to content
Fencer Vulns
medium 5.3

CVE-2024-36107 json

Information disclosure in minio

published 2024-05-28 2 y ago modified 2026-10-08 32 d ago also EUVD-2024-1541 , GHSA-95fr-cm4m-q5p9 , GO-2024-2886

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 50%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/minio/minio 0.0.0-20240527191746-e0fe7cc39172
  • minio minio RELEASE.2024-05-27T19-17-46Z

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-36107 updated cvss 5.3

minio: sensitive information exposure

  • Red Hat build of Apache Camel 4 for Quarkus 3 minio
    affected: workaround, no fix planned “Will not fix”
  • Red Hat build of Apache Camel for Spring Boot 3 minio
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat Integration Camel K 1 minio
    affected: workaround, no fix planned “Will not fix”
  • Red Hat build of Apache Camel for Spring Boot 4 minio Red Hat build of Quarkus minio
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/minio/minio
<0.0.0-20240527191746-e0fe7cc39172
0.0.0-20240527191746-e0fe7cc39172

Affected products

  • minio minio

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.