dbcve.org
MinioApplication

CVE-2023-25812

HIGH · 8.8 CVSS v3.1 Published 2023-02-21
Fix available
A fix is available. Upgrade to 2023-02-17t17-52-43z or later.
See remediation →
94/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click Patch available

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. Affected versions do not correctly honor a `Deny` policy on ByPassGoverance. Ideally, minio should return "Access Denied" to all users attempting to DELETE a versionId with the special header `X-Amz-Bypass-Governance-Retention: true`. However, this was not honored instead the request will be honored and an object under governance would be incorrectly deleted. All users are advised to upgrade. There are no known workarounds for this issue.

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

A detailed technical summary for this CVE is being prepared.

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:>= 2020-04-10t03-34-42z, < 2023-02-17t17-52-43z

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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-02-17t17-52-43z or later
Fixed in 2023-02-17t17-52-43z
Vendor patch github.com →
Recommended fix High confidence

Minio RELEASE.2023-02-17T17-52-43Z or later

  1. 1. Identify current Minio version by checking the minio server --version output or examining the running container/image tag
  2. 2. Backup all Minio data and configuration, including the backend storage and minio config file (typically at /etc/minio/config.json or in the deployment's config path)
  3. 3. Stop the Minio service gracefully to prevent data corruption during upgrade
  4. 4. For container deployments: Update the container image to tag '2023-02-17t17-52-43z' or later (e.g., minio/minio:2023-02-17t17-52-43z)
  5. 5. For binary installations: Download the new minio binary from https://github.com/minio/minio/releases/tag/RELEASE.2023-02-17T17-52-43Z and replace the existing binary
  6. 6. Verify the Minio server starts successfully with the new version
  7. 7. Confirm the upgrade was successful by running 'minio --version' and verifying output shows version 2023-02-17t17-52-43z or later
  8. 8. Test that governance retention policies are now properly enforced by attempting a DELETE operation with X-Amz-Bypass-Governance-Retention header on a governed object (should now return Access Denied)
Caveat Ensure any dependent client applications are compatible with the 2023-02-17 release as minor API behavior changes may occur

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25812 — 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-25812 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