Executive Summary

This vulnerability occurs because Apache CloudStack does not properly clean up MinIO policies when a bucket is deleted. As a result, users who previously owned a bucket can retain access to it even after deletion.

If another user creates a new bucket with the same name as the deleted one, the previous owners can use their old access and secret keys to gain unauthorized read and write access to the new bucket.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can lead to unauthorized access to data stored in buckets. Previous owners of a deleted bucket may gain read and write access to a new bucket with the same name, potentially exposing sensitive information or allowing malicious modifications.

The CVSS score of 8.0 indicates a high severity, meaning the impact on confidentiality, integrity, and availability can be significant.

Useful 0 Not Useful 0

Mitigation Strategies

Users are recommended to upgrade to Apache CloudStack versions 4.20.3.0 or 4.22.0.1, or later, which fixes this issue.

Useful 0 Not Useful 0

Compliance Impact

This vulnerability allows previous owners of deleted buckets to retain unauthorized read and write access if a new bucket with the same name is created by another user. Such unauthorized access to data can lead to violations of data protection and privacy regulations.

Specifically, this could impact compliance with standards like GDPR and HIPAA, which require strict controls over access to personal and sensitive data. Unauthorized access due to improper cleanup of access policies may result in data breaches, leading to non-compliance with these regulations.

Useful 0 Not Useful 0