dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 12 May 2023.
MinioApplication

CVE-2023-28432

HIGH · 7.5 CVSS v3.1 Published 2023-03-22
Fix available
A fix is available. Upgrade to 2023-03-20t20-16-18z or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

MinIO cluster deployments prior to RELEASE.2023-03-20T20-16-18Z have an information disclosure vulnerability where the API returns all environment variables, including sensitive credentials MINIO_SECRET_KEY and MINIO_ROOT_PASSWORD, to callers.

MitigationUpgrade MinIO to RELEASE.2023-03-20T20-16-18Z or later. Rotate any exposed credentials immediately after upgrading.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MinioApplication
Affected:>= 2019-12-17t23-16-33z, < 2023-03-20t20-16-18z

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify MinIO version
    Run 'minio --version' or check the binary/package version. If running via Docker, check the image tag. For cluster deployments, check via MinIO admin info API at /minio/v2/info or mc admin info command.
    Affected if Version is RELEASE.2019-12-17T23-16-33Z or later but earlier than RELEASE.2023-03-20T20-16-18Z
  2. Confirm MinIO admin API accessibility
    Verify the MinIO admin API endpoint is reachable on the configured port (typically port 9000 or custom admin port). Test with: curl -k https://<minio-host>:9000/minio/v2/
    Affected if Admin API responds to requests, indicating the service is exposed
  3. Test for environment variable exposure
    Send an authenticated admin API request (if authentication is configured) or unauthenticated request to endpoints that return service configuration or environment information, such as /minio/v2/service/trace or similar debug endpoints. Check response for presence of MINIO_SECRET_KEY or MINIO_ROOT_PASSWORD in the output.
    Affected if API response contains environment variable names MINIO_SECRET_KEY or MINIO_ROOT_PASSWORD with their values exposed

You are affected if your MinIO version falls within the range RELEASE.2019-12-17T23-16-33Z through RELEASE.2023-03-20T20-16-18Z and your admin API returns environment variables including sensitive credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2023-03-20t20-16-18z or later
Fixed in 2023-03-20t20-16-18z
Interim mitigation

Upgrade MinIO to RELEASE.2023-03-20T20-16-18Z or later. Rotate any exposed credentials immediately after upgrading.

Recommended fix High confidence

RELEASE.2023-03-20T20-16-18Z or later

  1. 1. Backup your Minio configuration, data, and environment files before proceeding.
  2. 2. Stop the Minio service on all nodes in the cluster.
  3. 3. Download Minio RELEASE.2023-03-20T20-16-18Z (or a later stable release) from the official Minio repository.
  4. 4. Replace the existing Minio binary with the new version on all cluster nodes.
  5. 5. Verify the binary integrity and permissions after installation.
  6. 6. Restart the Minio service on all cluster nodes.
  7. 7. Confirm that the /minio/v2/info/cluster API endpoint no longer returns sensitive environment variables like MINIO_SECRET_KEY or MINIO_ROOT_PASSWORD.
Caveat Standard Minio upgrade considerations apply - review release notes for breaking changes between your current version and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Minio Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-28432 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-28432 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data