LiveActive security incident?Get immediate response
CVE Record

CVE-2022-31028: Possible DDOS by establishing keep-alive connections with anonymous HTTP clients in MinIO

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.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

MinIO servers in the affected release range can be exhausted by anonymous HTTP clients that keep connections open. The business impact is service disruption, especially for public-facing object storage. The sources name a patched release and a reverse-proxy workaround.

Executive priority

Prioritize remediation for public-facing MinIO. The vulnerability can interrupt object storage availability, which may affect applications, backups, data pipelines, or customer-facing services that depend on MinIO.

Technical view

CVE-2022-31028 is a CWE-400 resource-consumption flaw in MinIO. Affected versions from RELEASE.2019-09-25T18-25-51Z through before RELEASE.2022-06-02T02-11-04Z can accumulate unending goroutines when clients keep HTTP connections established, leading to availability loss.

Likely exposure

Exposure is highest for internet-facing MinIO deployments running affected releases. Internal deployments may still be exposed where untrusted or compromised clients can open persistent HTTP connections to MinIO.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. The issue is network reachable, requires no privileges or user interaction, and primarily affects availability rather than confidentiality or integrity.

Researcher notes

CVSS 3.1 is 7.5 with AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. The advisory identifies affected releases and the patched release. Evidence provided supports denial-of-service risk only, not data theft, tampering, or confirmed in-the-wild exploitation.

Mitigation direction

  • Upgrade MinIO to RELEASE.2022-06-02T02-11-04Z or later.
  • Place a reverse proxy in front of MinIO where immediate upgrade is delayed.
  • Configure the proxy to limit attempted connections to MinIO.
  • Reject connections from clients exhibiting malicious keep-alive behavior.
  • Check MinIO vendor guidance before applying compensating controls.

Validation and detection

  • Inventory all MinIO deployments and record their exact release versions.
  • Confirm no deployment runs within the affected release range.
  • Identify whether any affected MinIO service is publicly reachable.
  • Verify reverse proxy connection limits protect any temporarily affected deployment.
  • Monitor for abnormal connection and goroutine growth around MinIO services.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-31028 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2022-31028Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
miniominio>= RELEASE.2019-09-25T18-25-51Z, < RELEASE.2022-06-02T02-11-04ZListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.