# CVE-2024-24747: MinIO unsafe default: Access keys inherit `admin` of root user, allowing privilege escalation

> Attackers with access keys can escalate privileges to admin level due to unsafe permission inheritance in MinIO object storage.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Jan 2024
- **Updated:** 1 Aug 2024
- **Also known as:** CLEANSTART-2026-VK24562, GHSA-xx8w-mq23-29g4, GO-2024-2499

## What is CVE-2024-24747?

CVE-2024-24747 is a high-severity vulnerability in minio, published on 31 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MinIO is a High Performance Object Storage. When someone creates an access key, it inherits the permissions of the parent key. Not only for `s3:*` actions, but also `admin:*` actions. Which means unless somewhere above in the access-key hierarchy, the `admin` rights are denied, access keys will be able to simply override their own `s3` permissions to something more permissive. The vulnerability is fixed in RELEASE.2024-01-31T20-20-33Z.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2024-24747?

3 open source packages ship an affected version, including github.com/minio/minio. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/minio/minio` | Go | All versions | 0.0.0-20240131185645-0ae4915a9391 |
| `github.com/minio/minio` | Go | All versions | 0.0.0-20240131185645-0ae4915a9391 |
| `github.com/minio/minio` | Go | All versions | 0.0.0-20240131185645-0ae4915a9391 |

Products: Minio Minio.

## How do I fix CVE-2024-24747?

Upgrade github.com/minio/minio to 0.0.0-20240131185645-0ae4915a9391 or later.

## Is CVE-2024-24747 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24747 exists.

Public exploit code:

- MinIO < 2024-01-31T20-20-33Z - Privilege Escalation (exploitdb)

## 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-2023-28432](https://insights.sbomify.com/CVE-2023-28432/): MinIO Information Disclosure (high 7.5, 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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-24747 and fix it if it is affected.

What it is: CVE-2024-24747 is a high-severity vulnerability in minio, published on 31 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24747 exists.

Affected packages and fixed versions:
- github.com/minio/minio (Go): affected all versions; fixed in 0.0.0-20240131185645-0ae4915a9391
- github.com/minio/minio (Go): affected all versions; fixed in 0.0.0-20240131185645-0ae4915a9391
- github.com/minio/minio (Go): affected all versions; fixed in 0.0.0-20240131185645-0ae4915a9391

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-2024-24747/ (Markdown: https://insights.sbomify.com/CVE-2024-24747/index.md)
```

## Sources

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

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