GPU VulnDB

Database/Control plane, storage & DevOps

Apache CloudStack: MinIO policies survive bucket deletion, giving a former owner access to a new bucket of the same name

CVSS 8.1CVE-2025-66467Control plane, storage & DevOpscurated

Impact

CloudStack does not remove the MinIO policy when a bucket is deleted. The access and secret keys the previous owner already holds stay valid for that bucket name, so when a different tenant later creates a bucket with the same name, the former owner reads and writes it. On a shared cluster that is cross-tenant access to object storage - the place training datasets, checkpoints and model artifacts live - and bucket names are predictable enough (team or project names) that collisions happen without the attacker doing anything clever. Write access is the sharper half: a tenant who can overwrite another tenant's checkpoints or datasets can poison training runs.

Who can reach it

Network, authenticated as an existing CloudStack user who previously owned a bucket and retained its generated access and secret keys. They then talk to the MinIO endpoint directly; no CloudStack admin rights and no access to the victim's account are needed.

What to do

Upgrade CloudStack to 4.20.3.0 or 4.22.0.1 or later, which fixes the cleanup. Upgrading the management server is a control-plane service restart, not a node drain - running instances and GPU workloads are unaffected. The fix is forward-looking: audit the existing MinIO policies for entries referencing buckets that no longer exist, or that no longer belong to the holder, and delete those plus the stale keys, otherwise already-leaked access persists after the upgrade.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.