authorization-audit

Audits server-side authorization enforcement across roles, resources, and actions to detect IDOR and privilege escalation.

Updated Aug 29, 2026
One-click install
npx skills add https://github.com/1arley/volibear --skill authorization-audit-1arley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: authorization-audit
Source: https://github.com/1arley/volibear/tree/main/.opencode/skills/authorization-audit
Command: npx skills add https://github.com/1arley/volibear --skill authorization-audit-1arley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Applications often confuse authentication with authorization, letting any logged-in user access or modify resources belonging to others. This Skill systematically audits whether the server enforces authorization for every resource access, catching IDOR, horizontal and vertical privilege escalation, and role-confusion bugs before they ship. ## Core Features & Use Cases - Authorization Matrix Analysis: Maps subject × action × resource cells and verifies each decision is enforced server-side, not just in the UI. - Attack Pattern Coverage: Tests IDOR, horizontal/vertical privilege escalation, participant-vs-owner confusion, role-from-client trust, and moderator scope bleed. - Evidence-Based Reporting: Classifies findings as CONFIRMED, HIGH CONFIDENCE, POSSIBLE, or SPECULATIVE with reproduction steps using two identities. - Use Case: Before launching a multi-tenant feature, audit endpoints like GET /order/{id} to confirm user A cannot read user B's orders and that ordinary users cannot invoke admin actions. ## Quick Start Audit this API's endpoints to verify that authorization is enforced server-side for every resource access, not just authentication.

Frequently Asked Questions about authorization-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test for IDOR vulnerabilities in an API?▼

IDOR testing involves manipulating resource identifiers in requests, such as changing /order/1000 to /order/1001, and checking whether the server returns another user's data. The audit reproduces access with two accounts and confirms the server rejects cross-user access with 403.

What is the difference between authentication and authorization?▼

Authentication verifies who you are, while authorization determines what you can do. A common bug is treating any authenticated user as authorized, letting logged-in users access resources they do not own.

How do I test for vertical privilege escalation?▼

Vertical escalation testing sends requests to admin or moderator endpoints using a regular authenticated user account. If the server returns success instead of 403, the endpoint lacks role enforcement and the finding is confirmed.

When is missing authorization a false positive?▼

It is a false positive when a middleware enforces authorization for the route, the resource is public by design, or the server ignores client-supplied roles and uses token claims instead. Always confirm the middleware covers the exact route before reporting.

Can client-side role checks replace server-side authorization?▼

No. Hiding buttons in the UI does not stop malicious users from calling the endpoint directly. Authorization decisions must be enforced server-side, ideally through centralized middleware plus ownership checks in each handler.