# CVE-2023-28432: MinIO Information Disclosure

> Attackers can retrieve sensitive environment variables, including root credentials, from MinIO cluster deployments, leading to potential unauthorized access.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Yes, since 21 Apr 2023 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Mar 2023
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-6xvq-wj2x-3h3q

## What is CVE-2023-28432?

CVE-2023-28432 is a high-severity vulnerability in minio, published on 22 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Minio is a Multi-Cloud Object Storage framework. In a cluster deployment starting with RELEASE.2019-12-17T23-16-33Z and prior to RELEASE.2023-03-20T20-16-18Z, MinIO returns all environment variables, including `MINIO_SECRET_KEY`
and `MINIO_ROOT_PASSWORD`, resulting in information disclosure. All users of distributed deployment are impacted. All users are advised to upgrade to RELEASE.2023-03-20T20-16-18Z.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-28432?

It affects 1 product.


Products: Minio Minio.

## How do I fix CVE-2023-28432?

No fix has been published for CVE-2023-28432 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 12 May 2023.

## Is CVE-2023-28432 being exploited?

Yes. Attackers have exploited CVE-2023-28432 in the wild since at least 21 Apr 2023.

Public exploit code:

- MinIO敏感信息泄露漏洞批量扫描poc&exp (github_poc): https://github.com/MzzdToT/CVE-2023-28432
- CVE-2023-28434 nuclei templates (github_poc): https://github.com/Mr-xn/CVE-2023-28432
- CVE-2023-28432 POC (github_poc): https://github.com/acheiii/CVE-2023-28432
- Automated vulnerability scanner for CVE-2023-28432 in Minio deployments, revealing sensitive environment variables. (github_poc): https://github.com/Chocapikk/CVE-2023-28432
- MiniO verify interface sensitive information disclosure vulnerability (CVE-2023-28432)  (github_poc): https://github.com/gobysec/CVE-2023-28432
- CVE-2023-28432 MinIO敏感信息泄露检测脚本 (github_poc): https://github.com/Cuerz/CVE-2023-28432

## Other vulnerabilities in minio

- [CVE-2023-28434](https://insights.sbomify.com/CVE-2023-28434/): MinIO Security Feature Bypass (high 8.8, exploited in the wild)
- [CVE-2020-11012](https://insights.sbomify.com/CVE-2020-11012/): Authentication bypass MinIO Admin API (critical 9.3)
- [CVE-2026-33322](https://insights.sbomify.com/CVE-2026-33322/): MinIO: JWT Algorithm Confusion in OIDC Authentication (critical 9.2)
- [CVE-2026-33419](https://insights.sbomify.com/CVE-2026-33419/): MinIO: LDAP login brute-force via user enumeration and missing rate limit (critical 9.1)
- [CVE-2026-40344](https://insights.sbomify.com/CVE-2026-40344/): MinIO has an Unauthenticated Object Write via Missing Signature Verification in Unsigned-Trailer Uploads (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-28432 and fix it if it is affected.

What it is: CVE-2023-28432 is a high-severity vulnerability in minio, published on 22 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2023-28432 in the wild since at least 21 Apr 2023.

Affected product: minio. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-28432/ (Markdown: https://insights.sbomify.com/CVE-2023-28432/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-28432
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-28432
- OSV: https://osv.dev/vulnerability/CVE-2023-28432

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-28432/
Summaries are generated and may contain mistakes; the official description above is the record.