Vulnerability from bitnami_vulndb
Published
2024-03-06 10:57
Modified
2025-05-20 10:02
Summary
Possible DDOS by establishing keep-alive connections with anonymous HTTP clients in MinIO
Details

MinIO is a multi-cloud object storage solution. Starting with version RELEASE.2019-09-25T18-25-51Z and ending with version RELEASE.2022-06-02T02-11-04Z, MinIO is vulnerable to an unending go-routine buildup while keeping connections established due to HTTP clients not closing the connections. Public-facing MinIO deployments are most affected. Users should upgrade to RELEASE.2022-06-02T02-11-04Z to receive a patch. One possible workaround is to use a reverse proxy to limit the number of connections being attempted in front of MinIO, and actively rejecting connections from such malicious clients.


{
  "affected": [
    {
      "package": {
        "ecosystem": "Bitnami",
        "name": "minio",
        "purl": "pkg:bitnami/minio"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2019.09.25"
            },
            {
              "fixed": "2022.06.02"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
          "type": "CVSS_V3"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2022-31028"
  ],
  "database_specific": {
    "cpes": [
      "cpe:2.3:a:minio:minio:*:*:*:*:*:*:*:*"
    ],
    "severity": "High"
  },
  "details": "MinIO is a multi-cloud object storage solution. Starting with version RELEASE.2019-09-25T18-25-51Z and ending with version RELEASE.2022-06-02T02-11-04Z, MinIO is vulnerable to an unending go-routine buildup while keeping connections established due to HTTP clients not closing the connections. Public-facing MinIO deployments are most affected. Users should upgrade to RELEASE.2022-06-02T02-11-04Z to receive a patch. One possible workaround is to use a reverse proxy to limit the number of connections being attempted in front of MinIO, and actively rejecting connections from such malicious clients.",
  "id": "BIT-minio-2022-31028",
  "modified": "2025-05-20T10:02:07.006Z",
  "published": "2024-03-06T10:57:16.966Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://gist.github.com/harshavardhana/2d00e6f909054d2d2524c71485ad02e1"
    },
    {
      "type": "WEB",
      "url": "https://github.com/minio/minio/pull/14995"
    },
    {
      "type": "WEB",
      "url": "https://github.com/minio/minio/releases/tag/RELEASE.2022-06-03T01-40-53Z"
    },
    {
      "type": "WEB",
      "url": "https://github.com/minio/minio/security/advisories/GHSA-qrpr-r3pw-f636"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-31028"
    }
  ],
  "schema_version": "1.5.0",
  "summary": "Possible DDOS by establishing keep-alive connections with anonymous HTTP clients in MinIO"
}


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 observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…