webapp-auth-bac
Webapp Auth Bac.
Files2
View on GitHubSKILL.mdskills/webapp-auth-bac/SKILL.md
GitHub--| | GET /admin/dashboard | 200 | 200 | 200 | 302 | Admin only | FAIL | | DELETE /api/users/{id} | 200 | 200 | 200 | 401 | Admin only | FAIL | | GET /api/users/other/profile | 200 | 200 | 200 | 401 | Own only | FAIL | | PUT /api/users/other/settings | 200 | 200 | 200 | 401 | Own only | FAIL | | GET /api/org/other-tenant | 200 | 200 | 200 | 401 | Same tenant | FAIL |
Critical Findings
- Vertical Escalation: Regular users can access /admin/* endpoints
- Horizontal IDOR: Users can read/modify other users' profiles
- Tenant Isolation: Cross-tenant data access via header manipulation
- Mass Assignment: Role escalation via profile update endpoint
Impact
- Complete administrative access for any authenticated user
- Full user data access across all accounts (15,000+ users)
- Cross-tenant data breach affecting 200+ organizations
- Account takeover via profile modification
Recommendation
- Implement server-side authorization checks on every endpoint
- Use a centralized authorization middleware/framework
- Enforce object-level authorization (verify ownership before access)
- Validate tenant context server-side, never from client headers
- Use allowlists for mass assignment (only permit expected fields)
- Implement audit logging for all access control decisions