ghsa-95fr-cm4m-q5p9
Vulnerability from github
Published
2024-05-29 18:37
Modified
2024-05-29 18:37
Summary
MinIO information disclosure vulnerability
Details

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 harsha@minio.io 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.

Show details on source website


{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/minio/minio"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.0.0-20240527191746-e0fe7cc39172"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2024-36107"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-200"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2024-05-29T18:37:14Z",
    "nvd_published_at": "2024-05-28T19:15:10Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\n[If-Modified-Since](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/If-Modified-Since)\n[If-Unmodified-Since](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/If-Unmodified-Since) \n\nHeaders when used with anonymous requests by sending a random object name requests you can figure\nout if the object exists or not on the server on a specific bucket and also gain access to some amount of\ninformation such as  \n\n```\nLast-Modified (of the latest version)\nEtag (of the latest version) \nx-amz-version-id (of the latest version)\nExpires (metadata value of the latest version)\nCache-Control (metadata value of the latest version)\n```\n\nThis conditional check was being honored before validating if the anonymous\naccess is indeed allowed on the metadata of an object.\n\n### Patches\nYes this issue has been already fixed in \n\n```\ncommit e0fe7cc391724fc5baa85b45508f425020fe4272 (HEAD -\u003e master, origin/master)\nAuthor: Harshavardhana \u003charsha@minio.io\u003e\nDate:   Mon May 27 12:17:46 2024 -0700\n\n    fix: information disclosure bug in preconditions GET (#19810)\n    \n    precondition check was being honored before, validating\n    if anonymous access is allowed on the metadata of an\n    object, leading to metadata disclosure of the following\n    headers.\n    \n    ```\n    Last-Modified\n    Etag\n    x-amz-version-id\n    Expires:\n    Cache-Control:\n    ```\n    \n    although the information presented is minimal in nature,\n    and of opaque nature. It still simply discloses that an\n    object by a specific name exists or not without even having\n    enough permissions.\n```\n\nUsers must upgrade to RELEASE.2024-05-27T19-17-46Z for the fix\n\n### Workarounds\nThere are no workarounds.\n\n### References\nRefer to the pull request #19810 for more information on the fix.",
  "id": "GHSA-95fr-cm4m-q5p9",
  "modified": "2024-05-29T18:37:14Z",
  "published": "2024-05-29T18:37:14Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/minio/minio/security/advisories/GHSA-95fr-cm4m-q5p9"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36107"
    },
    {
      "type": "WEB",
      "url": "https://github.com/minio/minio/pull/19810"
    },
    {
      "type": "WEB",
      "url": "https://github.com/minio/minio/commit/e0fe7cc391724fc5baa85b45508f425020fe4272"
    },
    {
      "type": "WEB",
      "url": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/If-Modified-Since"
    },
    {
      "type": "WEB",
      "url": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/If-Unmodified-Since"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/minio/minio"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "MinIO information disclosure vulnerability"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.