{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-25812 exists.","fix":"No fix has been published for CVE-2023-25812 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-25812 is a medium-severity missing authorization vulnerability in minio, published on 21 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-25812 and fix it if it is affected.\n\nWhat it is: CVE-2023-25812 is a medium-severity missing authorization vulnerability in minio, published on 21 Feb 2023. 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-2023-25812 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-2023-25812/ (Markdown: https://insights.sbomify.com/CVE-2023-25812/index.md)","id":"CVE-2023-25812","markdown":"https://insights.sbomify.com/CVE-2023-25812/index.md","name":"CVE-2023-25812","record":{"aliases":["GHSA-c8fc-mjj8-fc63"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Minio object storage","requires_auth":"none","summary":"Attackers can bypass governance retention policies to delete protected objects in Minio object storage, leading to unauthorized data modification.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"minio","vendor":"minio"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-281","name":"Improper Preservation of Permissions"}],"description":"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.","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":"Allowed DELETE on resources on object locked buckets under Governance mode in Minio","id":"CVE-2023-25812","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"SQL Injection via replacements in sequelize","id":"CVE-2023-25813"},"packages":[],"prev":{"headline":"Persistent Cross site scripting (XSS) in Uptime Kuma","id":"CVE-2023-25811"},"products":["minio"],"published":"2023-02-21","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-03-10","vendors":["minio"]},"summary":"Attackers can bypass governance retention policies to delete protected objects in Minio object storage, leading to unauthorized data modification.","url":"https://insights.sbomify.com/CVE-2023-25812/"}