{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31028 exists.","fix":"No fix has been published for CVE-2022-31028 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-31028 is a high-severity denial of service vulnerability in minio, published on 3 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-31028 and fix it if it is affected.\n\nWhat it is: CVE-2022-31028 is a high-severity denial of service vulnerability in minio, published on 3 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31028 exists.\n\nAffected product: minio. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-31028/ (Markdown: https://insights.sbomify.com/CVE-2022-31028/index.md)","id":"CVE-2022-31028","markdown":"https://insights.sbomify.com/CVE-2022-31028/index.md","name":"CVE-2022-31028","record":{"aliases":["GHSA-qrpr-r3pw-f636"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Object storage server","requires_auth":"none","summary":"Attackers can cause denial of service in MinIO by establishing keep-alive connections that lead to unending go-routine buildup.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"minio","vendor":"minio"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Possible DDOS by establishing keep-alive connections with anonymous HTTP clients in MinIO","id":"CVE-2022-31028","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"Authenticated XSS in Pi-hole AdminLTE","id":"CVE-2022-31029"},"packages":[],"prev":{"headline":"Authorization Bypass Through User-Controlled Key when using CILogonOAuthenticator in oauthenticator","id":"CVE-2022-31027"},"products":["minio"],"published":"2022-06-03","related":[{"cvss_score":8.8,"headline":"MinIO Security Feature Bypass","id":"CVE-2023-28434","kev_date_added":"2023-09-19","published":"2023-03-22"},{"cvss_score":7.5,"headline":"MinIO Information Disclosure","id":"CVE-2023-28432","kev_date_added":"2023-04-21","published":"2023-03-22"},{"cvss_score":9.3,"headline":"Authentication bypass MinIO Admin API","id":"CVE-2020-11012","kev_date_added":null,"published":"2020-04-23"},{"cvss_score":9.2,"headline":"MinIO: JWT Algorithm Confusion in OIDC Authentication","id":"CVE-2026-33322","kev_date_added":null,"published":"2026-03-24"},{"cvss_score":9.1,"headline":"MinIO: LDAP login brute-force via user enumeration and missing rate limit","id":"CVE-2026-33419","kev_date_added":null,"published":"2026-03-24"},{"cvss_score":8.8,"headline":"MinIO has an Unauthenticated Object Write via Missing Signature Verification in Unsigned-Trailer Uploads","id":"CVE-2026-40344","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":8.8,"headline":"MinIO has an Unauthenticated Object Write via Query-String Credential Signature Bypass in Unsigned-Trailer Uploads","id":"CVE-2026-41145","kev_date_added":null,"published":"2026-04-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["minio"]},"summary":"Attackers can cause denial of service in MinIO by establishing keep-alive connections that lead to unending go-routine buildup.","url":"https://insights.sbomify.com/CVE-2022-31028/"}