Authorization / Broken Access Control
A route through the library rather than a dump of it. Items are drawn from the full AuthZ collection, filtered to teaching material (news items are excluded) and ordered within each stage by depth signals — whether the piece carries code, how substantial it is, and what readers actually open.
1
Start here
5 resourcesOrientation and first principles — what the bug class is and how it behaves.
- Insecure Direct Object Reference (IDOR) Attack Guide | HackviserGuide to Insecure Direct Object Reference (IDOR) vulnerabilities, detailing manual testing techniques across URL parameters, POST bodies, HTTP headers, cookies, and file access. It covers automated discovery using tools like Burp Suite and ffuf, scripting with Python, and various attack vectors including numeric, UUID, hash-based, parameter pollution, and mass assignment bypasses, as well as blind IDOR exploitation.
- IDOR, The Beginner’s Goldmine: The Bug Bounty Field ManualLibrary for identifying Insecure Direct Object References (IDORs), a beginner-friendly vulnerability class common in bug bounty hunting. It details five recurring IDOR patterns, including sequential IDs (like in GitLab Model Registry), GraphQL node substitution, session object misbinding, cross-tenant boundary failures, and error response leakage. The guide emphasizes the mindset of questioning authorization and provides a step-by-step hunting methodology, recommending minimal tools like Burp Suite and two test accounts for confirmation.
- Preventing broken access control in express Node.js applicationsLibrary detailing broken access control vulnerabilities in Express Node.js applications, covering scenarios like unprotected admin panels, predictable user IDs leading to IDOR, and insecure direct object references. It illustrates how to prevent issues such as vertical privilege escalation and horizontal data exposure, emphasizing the risks of clear text logging and insufficient CSRF protection within Express middleware.
- RBAC vs ABAC vs ReBAC: How to Choose Access Control ModelsLibrary comparing Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC), and Relationship-Based Access Control (ReBAC). It details how RBAC, while simple, suffers from "Role Explosion" due to complexity in systems like AWS IAM and Kubernetes. ABAC is presented as a solution, using attributes and dynamic evaluation instead of static roles, exemplified by OPA and AWS IAM's Condition blocks. ReBAC principles are also touched upon, particularly in the context of Azure's resource hierarchy inheritance.
- Defending Against Broken Access ControlLibrary for defending against Broken Access Control (BAC), the #1 threat (A01:2021) in the OWASP Top 10. This vulnerability occurs when applications fail to enforce authorization, allowing unauthorized users to access data or functions. Learn about common attack techniques like Horizontal and Vertical Privilege Escalation, Parameter Tampering, IDOR, Data Exposure, API Abuse, and BOLA. The resource highlights real-world examples such as the Optus data breach and the Kia vehicle control vulnerability, emphasizing the critical need for robust server-side authorization.
2
Build depth
5 resourcesReal testing methodology, tooling, and writeups that show the work.
- Authorization Testing Automation Cheat Sheet - OWASPCheat sheet offering a methodology for automating authorization tests by formalizing an authorization matrix in XML. This approach enables the creation of integration tests that validate access controls for REST services across different logical roles like ANONYMOUS, BASIC, and ADMIN. The process involves defining roles, services with their associated permissions, and test payloads to ensure new feature additions or modifications do not conflict with existing authorization definitions.
- Authorization Cheat Sheet - OWASPCheatsheet providing guidance for robust authorization logic, addressing concerns like Broken Access Control, a top OWASP 2021 vulnerability. It details implementing "Least Privileges" by granting only necessary permissions and adopting a "Deny by Default" approach for all requests, emphasizing the need for validation on every interaction to prevent unauthorized access to resources, which can impact confidentiality, integrity, and availability.
- Formie missing authorization leads to SSTILibrary for identifying and mitigating vulnerabilities in the Formie Craft CMS plugin. It addresses a missing authorization flaw in the `EmailController` that allows any authenticated user to trigger Server-Side Template Injection (SSTI) by sending spoofed emails or rendering arbitrary notification content through Twig templating. The issue, identified as GHSA-wm3q-jh2w-mm72, was missed during previous security updates.
- GraphQL BOLA: one object, many paths, and how to prove the gapLibrary for identifying and exploiting GraphQL BOLA vulnerabilities. It details how to enumerate all potential paths to an object from a GraphQL schema, including those exposed via interfaces like `Node` or unions. The library aids in constructing single requests to test multiple resolvers with different accounts, facilitating the detection of authorization gaps where one path might have checks while others do not, a common issue highlighted by OWASP API Security Top 10 2023 (API1:2023).
- Cross-tenant quarantine IDOR in MailWatch (CVE-2026-85749)Writeup detailing CVE-2026-85749, a cross-tenant quarantine IDOR vulnerability in MailWatch v1.2.26. This flaw allowed any authenticated user to release or permanently delete quarantined mail belonging to other users or domains by exploiting a discrepancy where the message viewer enforced tenant scope, but the quarantine action endpoint did not. The vulnerability, rated High (CVSS 8.1) and categorized under CWE-639 and CWE-566, was fixed in version 1.2.27 by consistently applying session filters in quarantine operations.
3
Go deep
8 resourcesNovel research, edge cases, and the techniques that push the class forward.
- Security Benchmarking Authorization Policy Engines: Rego, Cedar, OpenFGAFramework for dynamically evaluating authorization policy engines, including Rego, Cedar, OpenFGA, and Teleport ACD. This system automates security benchmarking and robustness testing by executing predefined test cases in isolated Docker containers for each engine, comparing actual results against expected outcomes to identify potential threats and vulnerabilities.
- How I Found a $113,337 AF_ALG Linux Local Privilege Escalation Before Copy FailLibrary detailing the discovery and exploitation of CVE-2025-39964, a Linux AF_ALG local privilege escalation vulnerability. This research uncovered an out-of-bounds access flaw in the kernel's handling of user-supplied data for cryptographic operations, allowing unprivileged users to gain root access and escape Docker containers. The vulnerability, present since 2011, stems from a race condition between writers sharing an AF_ALG socket, distinct from the later disclosed "Copy Fail" bug.
- AI Agent Authorization Beyond Authentication: A Look At AWS DogwoodLibrary for AI agent authorization, AWS Dogwood, builds on Cedar to incorporate temporal policy, evaluating sequences of prior actions beyond point-in-time requests for tool calls. This temporal policy addresses risks from sequences of seemingly benign actions, such as the "lethal trifecta" of reading sensitive files and then exfiltrating them. GitGuardian's Secret Analyzer provides permission context and the Exploration Map traces consumers and resources, aiding migration from long-lived secrets as AI-related leaks grew significantly.
- Privilege escalation from IIS AppPool to NT Authority/SYSTEM via AD CS RPC endpointTechnique detailing privilege escalation from IIS AppPool to NT Authority\SYSTEM within an Active Directory domain. This method leverages a Windows behavior where IIS AppPool identities accessing network resources are elevated to the host's machine account. The technique involves submitting a Certificate Signing Request to the Active Directory Certificate Services (AD CS) RPC endpoint, obtaining a machine account certificate, and then using the S4U2Self technique with tools like Rubeus to impersonate administrator accounts.
- NvRoot (CVE-2026-47591) where in neocloud multi-tenant GPU environments, rent = root. Essentially it's a dirty page cache LPE using GPUs as catalyzerLibrary for detecting NVIDIA driver vulnerabilities like CVE-2026-47591 (NvRoot), a local privilege escalation impacting multi-tenant GPU environments. This exploit leverages a flaw in GPU memory pinning permissions to allow a GPU to write to read-only files, enabling overwriting setuid binaries for root access. Traditional security tools miss this, as it resembles legitimate CUDA operations. The library instruments the NVIDIA driver and CUDA runtime to identify contradictory pins and unexpected writes to critical system files.
- Cross-account JS execution in Basecamp Fizzy: five chained bugs to token theftAnalysis of five chained vulnerabilities in Basecamp Fizzy chained by Pirikara that allowed cross-account JavaScript execution and API token theft. The attack chain exploited parameter forwarding in URL builders, parameterized HTML content types bypassing exact-string checks, orphaned blob authorization defaults, Turbo Frame script execution with CSP nonce laundering, and same-origin script access to the token endpoint.
- Leveraging undocumented CodeConnection APIs in a CodePipeline build job or SageMaker Studio Notebook to enumerate, clone, push and delete code repositories.Library detailing privilege escalation techniques within AWS CodePipeline and SageMaker Studio. It explains how an improperly configured "Full clone" output artifact format for CodeConnections, combined with insufficient IAM role restrictions, allows attackers to enumerate, clone, push, and delete repositories from the source code provider. The library specifically covers the use of undocumented CodeConnection APIs and the implications of the `codeconnections:UseConnection` and `codestar-connections:UseConnection` IAM permissions.
- The skb that wasn't freed - the Fragnesia primitive via Open vSwitchTool for privilege escalation exploiting the Fragnesia primitive in Open vSwitch. This vulnerability, tracked as CVE-2026-90049, CVE-2026-89487, and CVE-2026-80977, arises when Open vSwitch incorrectly strips the `SKBFL_SHARED_FRAG` marker from packets, allowing unprivileged users to overwrite read-only memory mappings and achieve local privilege escalation on affected distributions with user namespaces enabled.