Details
If upgrading is not immediately possible:
- Rotate the root credential and restrict who holds it. The exploit requires a JWT signed with
MINIO_ROOT_PASSWORD. Treat the root credential as the host-filesystem disclosure primitive that it is: rotate it after any suspected exposure, store it only in the secret manager that bootstraps the cluster, and do not hand it to applications or operators who only need object-level access.
- Do not run the MinIO container as UID 0. Set
securityContext.runAsNonRoot: true(and a non-zerorunAsUser) in Kubernetes manifests, or add--usertodocker run. This reduces the blast radius from arbitrary host-filesystem disclosure to MinIO-UID-owned files only.
- Restrict the internode storage-REST port at the network layer. In distributed deployments, the storage-REST route is served on the same port as the S3 API by default. Where feasible, use
--internode-portto expose internode traffic on a separate interface reachable only from other cluster peers, and block that interface from client networks.
Credits
- Finders: Discovered by Claude, Anthropic's AI assistant, and triaged by Adrian Denkiewicz at Doyensec in collaboration with Anthropic Research.
Resources