Uniform Bucket-Level Access Not Enabled
The bucket uses fine-grained access control, so individual objects can carry their own ACLs that grant access the bucket's IAM policy does not show.
| Severity | Low |
| CVSS 3.1 | 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N Open in the calculator |
| CVSS 4.0 | 6.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-732: Incorrect Permission Assignment for Critical Resource |
| OWASP Top 10 | A01:2025 Broken Access Control |
| MITRE ATT&CK | T1530 Data from Cloud Storage |
| Category | Security Misconfiguration |
Description
Cloud Storage offers two ways of controlling access to a bucket's objects. With uniform bucket-level access, only IAM policies apply, set on the bucket or inherited from the project, folder and organisation. With fine-grained access control, each object can also carry its own access control list (ACL), which can grant read or write access to users, groups, project roles, or the public principals allUsers and allAuthenticatedUsers.
The finding applies where buckets use fine-grained access control without a need for it. The setting does not expose data by itself, but object-level grants, accidental public grants among them, do not appear in the bucket's IAM policy, so a review of IAM alone can miss objects that are shared more widely, including objects uploaded with a predefined ACL such as publicRead. Auditing per-object ACLs across many objects is impractical, and mistakes made at upload time persist unnoticed.
Objects may therefore be readable by people the organisation believes have no access, and an attacker who learns or guesses the name of such an object can read it. The risk is greatest for buckets that receive uploads from many systems or users, and lowest where public access prevention is enforced, since that blocks public ACLs regardless of this setting.
The weakness is identified from each bucket's configuration, for example with gcloud storage buckets describe, where uniform bucket-level access is shown as disabled, and from the organisation policies in force, where the constraints/storage.uniformBucketLevelAccess constraint is not enforced.
Remediation
- Before switching, review the bucket's object ACLs and move any access that is genuinely needed into IAM bindings on the bucket, because object ACLs stop applying once uniform access is enabled.
- Enable uniform bucket-level access on each bucket. It can be reversed within 90 days, after which it becomes permanent.
- Enforce the
constraints/storage.uniformBucketLevelAccessorganisation policy constraint so that new buckets are created with uniform access. - Enforce public access prevention as well, so that no public grant can be made through either mechanism.
Confirm the fix by describing each bucket and checking that uniform bucket-level access is enabled, and that objects which should not be shared can no longer be read by principals outside the bucket's IAM policy.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.