T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:90- Finding
Subscription-Wide Azure Roles Exceed the Minimum Permissions Required
- Content
View full analysis
### Step 2: Add Security Reader Role az role assignment create --assignee --role "Security Reader" --scope /subscriptions/ ``` The corresponding role configuration is: ```json { "role": "Reader", "scope": "Subscription", "reason": "Read access to all resource configurations (storage, compute, network, SQL, App Service)", "built_in_id": "acdd72a7-3385-48ef-bd42-f606fba81ae7" }, { "role": "Security Reader", "scope": "Subscription", "reason": "Read access to Microsoft Defender for Cloud status and security recommendations", "built_in_id": "39bc4728-0917-49c7-9d2c-d95423bc2eb4" } ``` ### Technical Analysis The Skill performs a limited set of configuration checks against Storage, Network Security Groups, Key Vault, SQL, Compute, App Service, and Defender pricing information. However, its setup instructions grant the built-in **Reader** and **Security Reader** roles across the entire subscription. These built-in roles provide visibility beyond the exact management-plane read operations used by the twelve declared checks. In particular, the policy states that Security Reader permits access to security recommendations, while the implementation only queries Defender pricing tiers. The behavior is read-only and does not permit direct Azure resource modification, but it violates least privilege by allowing broad subscription reconnaissance if the scanner identity is compromised. ### Attack Path 1. An operator follows the documented setup and grants Reader and Security Reader at subscription scope. 2. The service-principal client secret is exposed through an unrelated ...[truncated 940 chars]- Remediation
View remediation
