Basic Owner or Editor Roles Granted

Users, groups or service accounts hold the basic Owner or Editor role, which grants broad rights over almost every resource in the project, folder or organisation.

SeverityMedium
CVSS 3.16.6 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H Open in the calculator
CVSS 4.07.5 CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Open in the calculator
CWECWE-1220: Insufficient Granularity of Access Control
MITRE ATT&CKT1078.004 Cloud Accounts, T1098.003 Additional Cloud Roles
CategoryBroken Access Control

Description

Google Cloud's basic roles, Owner, Editor and Viewer, predate its predefined roles and apply across almost every service. Editor allows a principal to create, change and delete most resources and to read most data in its scope. Owner adds the ability to manage IAM policies, and so to grant any role to anyone. Every principal holding a basic role is a route to broad control of the resources in its scope, and Google recommends against using basic roles where predefined or custom roles can be used instead, particularly in production.

The finding applies where Owner or Editor is granted to users, groups or service accounts that need far narrower access, for example developers who deploy one service, support staff who restart instances, or automation that writes to one bucket. An attacker who compromises one of these accounts, through phishing, a leaked service account key or a compromised workload, can read and change data, deploy resources and, with Owner, grant themselves or others further access for persistence. Because the roles are far wider than the holders' duties, a compromise that should have been contained to one service affects the whole project or more.

Grants made at folder or organisation level are inherited by every project beneath, multiplying their effect, so the impact is greatest for those grants and for service accounts used by exposed workloads. Grants to accounts outside the organisation's domain, such as personal Gmail accounts, are a related and common weakness.

The finding is identified by reviewing the IAM policies of the organisation, folders and projects, for example with gcloud asset search-all-iam-policies filtered on roles/owner and roles/editor. The IAM role recommender compares the permissions each principal holds with those it has actually used, and suggests smaller roles.

Remediation

  • Replace each Owner and Editor grant with the predefined or custom roles that cover the holder's actual duties, granted at the narrowest scope that works. The IAM role recommender's suggestions are a good starting point.
  • Reserve Owner for a small, named administrative group, preferably granted only temporarily through Privileged Access Manager or IAM Conditions with an expiry, and remove basic roles from service accounts.
  • Remove basic role grants at organisation and folder level unless there is a documented need, since they apply to every project beneath.
  • Grant roles to groups rather than to individual users, and enforce the constraints/iam.allowedPolicyMemberDomains organisation policy constraint so that roles can be granted only to identities in the organisation's own domains.
  • Alert on IAM policy changes that grant basic roles, using the Admin Activity audit logs.
gcloud projects remove-iam-policy-binding "$PROJECT_ID" --member="user:$USER_EMAIL" --role=roles/editor

Confirm the fix by searching the IAM policies again and finding basic role grants only where they are documented and approved.

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 trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Google Cloud Findings

Every Google Cloud finding