Authorization / Broken Access Control
Authorization vulnerabilities occur when applications fail to properly enforce access controls, allowing users to perform actions or access resources beyond their intended permissions. Broken Access Control consistently ranks as the #1 risk in the OWASP Top 10, encompassing issues like privilege escalation (both vertical and horizontal), missing function-level access controls, and insecure direct object references at the authorization layer. Unlike authentication (verifying who you are), authorization determines what you are allowed to do — and flaws here can expose entire administrative interfaces, allow users to modify other accounts, or grant elevated privileges through parameter tampering, forced browsing, or JWT manipulation. Modern applications with complex role hierarchies, microservice architectures, and API-first designs face particular challenges in maintaining consistent authorization checks across every endpoint and resource.
Access control fails at design time, which is why testing it is hard
Broken access control heads the OWASP Top Ten, and the reason is not that developers forget to write checks. It is that authorization is a cross-cutting property that no single place in a codebase owns. Every new endpoint, every new role, every new tenant relationship is another opportunity for the rule that exists conceptually to not exist in one particular code path — and nothing in the type system, the framework or the test suite will notice.
It is worth separating the two failure modes, because they are found differently. Function-level failures mean a user can reach an operation their role should not permit: an administrative endpoint with no role check, a privileged action exposed because the UI merely hid the button. These are found by enumerating endpoints and replaying them as a lower-privileged user. Object-level failures mean the operation is allowed but the target is not the user's — the IDOR case — and these are found by replaying one account's requests with another account's session and looking at what comes back.
Multi-tenancy makes both worse, because the boundary being crossed is commercial rather than technical and the check is often a single column in a query that someone omitted. Inheritance and delegation features — shared workspaces, team roles, "act as" support tooling — are consistently the richest ground, since they intentionally grant access across boundaries and therefore contain the code paths that were written to say yes.
Testing this systematically means building a matrix before you start: every role, every object type, every operation, and a plan for what a successful check looks like. That sounds bureaucratic and is the only approach that finds these reliably, because the bugs are in the cells nobody thought about. Burp's Autorize and similar tooling automates the replay half; deciding what the matrix contains remains manual.
On defence, the durable pattern is centralized enforcement on the data access layer rather than scattered checks in controllers — deny by default, and make the tenant or owner constraint structurally impossible to omit.
| Date Added | Link | Excerpt |
|---|---|---|
| 2026-11-19 NEW 2026 | Authentication vs Authorization: The Difference, and How to Actually Secure an API beginner API Sec AuthN | Confusing authentication and authorization is a primary cause of API breaches. Authentication verifies a user's identity, confirming *who* they are, while authorization determines what authenticated users are *allowed* to do. Properly securing an API requires understanding and correctly implementing both. |
| 2026-11-19 NEW 2026 | MCP Authorization — Part 1: Overview, Server Design, and Implementation intermediate | This article provides a practical guide to designing and implementing authorization for a protected HTTP MCP server. It covers the overview, server design, and implementation details for handling requests to an MCP server, which serves AI functionalities. The content focuses on the technical aspects of securing these servers and managing access control effectively. |
| 2026-11-19 NEW 2026 | SGLang missing authorization news AI | SGLang versions up to 0.5.23 are affected by a missing authorization vulnerability. This flaw, patched in commit 7b5fb39, allows unauthorized access or actions within the system. Users are advised to update to a version that includes the fix to mitigate this security risk. The specific impact and details of the vulnerability are addressed in the referenced commit. |
| 2026-11-19 NEW 2026 | Frappe ERPNext missing authorization in financial reports news | Frappe ERPNext versions prior to 16.35.0 suffer from a critical authorization vulnerability in their financial reports. This flaw allows unauthorized users to access sensitive financial data, potentially leading to data breaches and compliance issues. Users are strongly advised to update to version 16.35.0 or later to patch this vulnerability and secure their financial information. |
| 2026-11-19 NEW 2026 | Attendize EventOrdersController authorization bypass news IDOR | Attendize, up to version 2.8.0, has a critical authorization bypass vulnerability in its `EventOrdersController`. This flaw allows unauthenticated users to access and modify order data, posing a significant security risk. Exploiting this vulnerability could lead to unauthorized access and manipulation of event order information. Users are strongly advised to update to a patched version to mitigate this security threat. |
| 2026-11-19 NEW 2026 | Fleet authorization bypass in deprecated endpoint news IDOR | Fleet versions prior to 4.92.0 are vulnerable to an authorization bypass. This vulnerability exists within a deprecated endpoint, allowing unauthorized access. Users are strongly advised to update to version 4.92.0 or later to mitigate this security risk. |
| 2026-11-19 NEW 2026 | django-filer missing per-object authorization news IDOR | A security vulnerability has been identified in django-filer concerning missing per-object authorization for version transitions. Specifically, the `discard` and `edit_redirect` operations are affected. This means that users might be able to perform these actions on file versions they shouldn't have access to, potentially leading to unauthorized modifications or deletions. |
| 2026-11-19 NEW 2026 | How I Found IDOR, SQLi and XSS on NASA intermediate Bug Bounty IDOR Recon SQLi XSS | In this write-up, Aditya Nail Emery details the discovery of three security vulnerabilities on a NASA subdomain: Insecure Direct Object Reference (IDOR), SQL Injection (SQLi), and Cross-Site Scripting (XSS). The post outlines the methodology used to find these critical security flaws within the NASA infrastructure. → infosecwriteups.com |
| 2026-11-19 NEW 2026 | Attendize cross-account authorization bypass news IDOR | Attendize versions up to 2.8.0 are vulnerable to a cross-account authorization bypass. This flaw allows an attacker to gain unauthorized access to other users' Attendize accounts. The vulnerability arises from insufficient access controls, enabling attackers to potentially manipulate or view data that should be restricted. This could lead to serious data breaches and compromise user privacy within the platform. Users are advised to update to a patched version to mitigate this security risk. |
| 2026-11-18 NEW 2026 | P2 Broken Access Control Allowing Unauthorized Account Email Modification and Account Takeover news AuthN Bug Bounty | A P2, high-severity vulnerability categorized as Broken Access Control allows for unauthorized modification of account email addresses and subsequent account takeover. This means an attacker could potentially change a user's registered email, gain control of their account, and access sensitive information or perform malicious actions. |
| 2026-11-18 NEW 2026 | How Trusting a Request Header Turned a Password Reset Into Account Takeover intermediate AuthN Bug Bounty | A vulnerability was discovered where trusting a request header during a password reset process led to account takeover. This exploit represents a classic web security flaw, distinct from other common vulnerabilities like IDOR and race conditions. The core issue involved improper validation of a header, allowing attackers to potentially manipulate the password reset mechanism and gain unauthorized access to user accounts. |
| 2026-11-18 NEW 2026 | Facebook IDOR: Deleting Any Photo Album (Case Study) intermediate Bug Bounty IDOR | A Facebook IDOR vulnerability allowed any user to delete any photo album they could view through the Graph API. The issue stemmed from a missing ownership check within the API's deletion endpoint. This meant that if a user had permission to view an album, they could also delete it. The vulnerability was patched by implementing proper ownership verification. → masimshahzad.medium.com |
| 2026-11-18 NEW 2026 | wishthis authorization bypass in User::ownsWish intermediate IDOR | Advisory for GHSA-rw9j-p262-6jvc detailing an authorization bypass vulnerability in wishthis 1.2.3 within the User::ownsWishlist() function. Exploiting this, authenticated users can modify other users' wishes and wishlists by supplying sequential wish_id and wishlist_id values to API handlers. This allows for editing, adding, renaming, or deleting wishes and wishlists, as documented in CVE-2026-130851 and various GitHub references. |
| 2026-11-18 NEW 2026 | EveryDocs Core authorization bypass intermediate IDOR | Writeup of GHSA-fphh-x7fg-5xpm, detailing an authorization bypass in EveryDocs Core before 1.6.1. This vulnerability enables authenticated users to access and manipulate other users' records, including documents, files, folders, tags, and people, by exploiting unscoped `Model.find(params[:id])` lookups. The exploit involves sequential ID enumeration. |
| 2026-11-17 NEW 2026 | Soft-Deleted, Still Editable: BOLA in Munshi’s Invoice API intermediate API Sec Bug Bounty | Munshi's Invoice API suffered from a Business Logic Flaw (BOLA) vulnerability. The API failed to properly check invoice ownership and lifecycle status, allowing authenticated users to edit financial data even after an invoice had been soft-deleted. This means that even though an invoice was marked as removed, its contents could still be altered by unauthorized individuals, potentially leading to financial data manipulation. |
| 2026-11-17 NEW 2026 | CBoard missing authorization intermediate | Vulnerability writeup detailing a missing authorization flaw in CBoard before commit 7bd8180. This allows any authenticated user to access sensitive administrative functions, including deleting users and querying configurations, due to bypassed AOP role checks in `AdminController` and `DashboardController`. This vulnerability is referenced by CVE-2026-130073 and GHSA-r8r7-2528-477c. |
| 2026-11-17 NEW 2026 | Silverstripe: auth bypass in GridFieldDetailForm intermediate | Advisory for CVE-2026-88989 in Silverstripe GridFieldDetailForm, allowing CMS users with record edit permissions to bypass creation restrictions by sending direct save requests. This vulnerability, reported by HDWSec, impacts the silverstripe/silverstripe-framework and has a reference in the GitHub Advisory Database. |
| 2026-11-17 NEW 2026 | Silverstripe: user-controlled ClassName allows unauthorized record type change intermediate | Advisory GHSA-4qv2-g5vp-wjjw details a vulnerability in Silverstripe where user-controlled ClassName in GridField allows unauthorized record type changes. An attacker who can edit a record can change its class to an unrelated type, bypassing permission checks for that new class. This vulnerability was reported by Lachlan Davidson of Carapace and is linked to CVE-2026-91113. |
| 2026-11-17 NEW 2026 | B3log Solo missing authorization in B3Receiver intermediate IDOR | Writeup of CVE-2026-130078 in B3log Solo, a missing authorization vulnerability affecting versions through 4.4.0. The flaw in B3Receiver.receiveArticle enables visitor accounts to overwrite any article's title, content, and tags by exploiting the POST /apis/symphony/article endpoint, particularly for OAuth-created visitors who can supply their username as userB3Key. |
| 2026-11-17 NEW 2026 | free5GC WebConsole authorization flaw in ChangePasswordInfo intermediate IDOR | An authorization flaw exists in the ChangePasswordInfo component of free5GC WebConsole, affecting versions up to 1.4.6. This vulnerability could allow unauthorized users to change passwords. The issue stems from improper access control within the ChangePasswordInfo functionality. |
| 2026-11-17 NEW 2026 | phpMyFAQ authorization bypass (critical) intermediate IDOR | Vulnerability writeup detailing an authorization bypass in phpMyFAQ versions 4.1.9 through 4.1.12 and 4.2.0-alpha through 4.2.0-RC.2. This flaw affects multisite configurations, enabling attackers to overwrite passkeys of accounts on different tenants by leveraging a shared PHP session store. Exploitation involves using WebAuthn prepare() on one tenant and replaying the session against `/api/webauthn/register` on another tenant or the master to achieve account takeover, as seen in CVE-2026-130369. |
| 2026-11-17 NEW 2026 | phpMyFAQ authorization bypass (4.2.0 RC) intermediate IDOR | This content describes a security vulnerability in phpMyFAQ versions 4.2.0-alpha through 4.2.0-RC.1. The flaw allows for an authorization bypass, potentially enabling unauthorized access or actions within the application. |
| 2026-11-17 NEW 2026 | phpMyFAQ authorization bypass intermediate IDOR | Advisory regarding CVE-2026-130383 in phpMyFAQ, affecting versions prior to 4.1.12 and 4.2.0-alpha.2 before 4.2.0-RC.2. This authorization bypass allows authenticated editors to manipulate search index documents via the `/admin/api/faq/update` endpoint, leading to potential data deletion or manipulation on Elasticsearch/OpenSearch deployments. |
| 2026-11-16 NEW 2026 | OWASP #5: Broken Function Level Authorization (When Users Execute Forbidden Actions) beginner API Sec | Broken Function Level Authorization (BFLA) is a critical API security vulnerability where users can access or perform actions they aren't permitted to. This occurs when an application fails to properly enforce access controls at the function or feature level, allowing a regular user to execute administrative functions. Attackers can exploit this by manipulating requests to bypass intended restrictions. Developers must ensure that authorization checks are applied rigorously to every function and resource. |
| 2026-11-16 NEW 2026 | AutomatorWP Pro webhook authorization bypass news | Library for identifying authorization bypass vulnerabilities, specifically detailing how versions of AutomatorWP Pro up to 1.4.4 allow unauthenticated attackers to reset any WordPress account's password, including administrators, via webhook configurations. This exploit is possible when an automation pairs a "Receive Webhook" trigger with an "Is the user ID" field to an "Update-User" action, with a blank User ID field and the password mapped to the webhook password tag. |
| 2026-11-16 NEW 2026 | Formie missing authorization leads to SSTI intermediate 6 min read SSTI | Library 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. |
| 2026-11-16 NEW 2026 | GraphQL Core Schema: critical account takeover news 2 min read AuthN GraphQL | Library module SA-CONTRIB-2026-316 (CVE-2026-126725) for GraphQL Core Schema in Drupal enables critical account takeover by insufficiently checking access during password changes via its API. This vulnerability, affecting versions prior to 1.0.29, allows any user with account viewing privileges to change another user's password, including administrators, provided the "User Login" schema extension is enabled. The fix involves upgrading the module or disabling the "User Login" extension as a mitigation, though the latter will break authentication functionality. |
| 2026-11-16 NEW 2026 | Laravel Temporary Signed URLs: Invalid Signature, Expiry, and IDOR intermediate IDOR | This article, assisted by AI and reviewed against Laravel 13.x documentation, discusses vulnerabilities related to temporary signed URLs. It focuses on three key issues: invalid signatures, which prevent URL verification; expiry problems, where URLs might not function as expected after their intended duration; and Insecure Direct Object References (IDORs). The content likely explores how these flaws can be exploited in Laravel applications, impacting the security and integrity of temporary signed URL functionality. |
| 2026-11-16 NEW 2026 | GeoPulse IDOR in GET endpoint intermediate IDOR | Library for securing applications against insecure direct object references, specifically detailing GHSA-6hh5-5g4m-3g64 impacting GeoPulse 1.5.0 through 2.3.0. The vulnerability, CVE-2026-129467, resides in the GET /api/v1/places/geocoding/{id} endpoint, allowing authenticated users to access other users' private location data by enumerating sequential `reverse_geocoding_location` IDs. This can expose custom place names, city, country, coordinates, and bounding boxes from user history. |
| 2026-11-15 NEW 2026 | Pulse missing authorization in /api/ai news AI API Sec | Advisory for CVE-2026-129428 detailing a missing authorization vulnerability in Pulse versions 5.0.17 before 6.8.0. The vulnerability exists in the `/api/ai/approvals` endpoints, allowing authenticated viewer-level users to manage approval requests. Attackers can exploit this to list pending requests, expose commands and targets, and approve or deny other users' requests, impacting decision and audit states. |
| 2026-11-15 NEW 2026 | Butler VM: Not Every Finding Was a Vulnerability — But One Path Led to SYSTEM intermediate Recon | This case study details a penetration test targeting Butler VM. While not all initial findings were critical vulnerabilities, the investigation of the Jenkins application proved fruitful. By analyzing network reconnaissance data and focusing on Windows access tokens, the tester discovered a critical vulnerability that ultimately led to SYSTEM-level access. The report outlines the specific path taken to achieve this high-privilege compromise. |
| 2026-11-15 NEW 2026 | Exploiting All 10 OWASP API Security Risks in vAPI (+ Bonus Arena Challenges) intermediate API Sec AuthN Bug Bounty | This content details a step-by-step walkthrough of exploiting all ten OWASP API Security Risks within vAPI, including bonus arena challenges. The process covers identifying and exploiting vulnerabilities such as Broken Object Level Authorization and Broken Authentication. |
| 2026-11-15 NEW 2026 | Frappe india-payroll missing authorization news Python | Advisory for a missing authorization vulnerability in Frappe india-payroll before 16.0.4, specifically within the `tax_regime_selector.py` file. This flaw impacts `get_employee_details`, `compute_tax_comparison`, and `set_tax_regime` methods, allowing authenticated, low-privileged users to view sensitive payroll data of other employees by supplying different employee identifiers. Attackers can also alter tax regimes for draft Salary Structure Assignments, impacting tax withholding. |
| 2026-11-15 NEW 2026 | graphql-orm-router: HTTP SSE/multipart subscriptions bypass WebSocket gateway auth controls news 4 min read API Sec AuthN GraphQL | Library for securing GraphQL HTTP SSE/multipart subscriptions. It addresses a vulnerability (GHSA-3qf7-j9r6-6qv3) where these subscription types bypass WebSocket gateway authentication, failing to enforce bearer tokens, token expiry, or attempt limits. The issue stems from how the router handles HTTP requests for subscriptions, which bypasses authorization checks applied to WebSocket connections. Suggested fixes include rejecting subscriptions from untrusted paths or enforcing authentication and expiry for HTTP streams. |
| 2026-11-15 NEW 2026 | Ryot 10.5.6 authorization bypass (IDOR) news IDOR | Advisory for Ryot before 10.5.6 details an authorization bypass vulnerability (IDOR) that enables authenticated users to revoke arbitrary access links. Attackers can exploit this by obtaining access link IDs from public share URLs and submitting them to the `revokeAccessLink` GraphQL mutation, bypassing ownership checks and disrupting shared access. This vulnerability is referenced by GHSA-qgc8-wm6f-pf7h and CVE-2026-127087. |
| 2026-11-15 NEW 2026 | OpenMage Magento-LTS IDOR news IDOR | A critical Insecure Direct Object Reference (IDOR) vulnerability has been identified in OpenMage Magento-LTS versions prior to 20.18.2 and 21.0.0-beta1. This flaw allows attackers to potentially access and manipulate sensitive data that they should not have permission to view or modify. Users are strongly advised to upgrade to a patched version of OpenMage Magento-LTS immediately to mitigate this security risk. |
| 2026-11-15 NEW 2026 | Zr.Admin.NET insecure direct object reference (high) news IDOR | Writeup on CVE-2026-129454 in Zr.Admin.NET, detailing an insecure direct object reference vulnerability. This flaw in `GET /workflow/instance/{instanceId}` allows authenticated users to view others' workflow instances, including sensitive form data and approval records, by enumerating sequential IDs. The vulnerability exists in commits from `85cff6a` through `eb9228a`. |
| 2026-11-15 NEW 2026 | LearnPress Course Wishlist 4.1.2 IDOR news IDOR | Library vulnerability GHSA-33v5-7wpw-28gp details an Insecure Direct Object Reference (IDOR) in LearnPress Course Wishlist Add-on versions prior to 4.1.2. Remote attackers can exploit the `load_content_via_ajax` REST route by supplying an arbitrary `user_id` parameter, bypassing session identity to manipulate any user's course wishlist. This allows attackers to add or remove courses and enumerate wishlisted courses across user and course IDs. |
| 2026-11-15 NEW 2026 | SurveyKing 1.12.0–1.13.2 authorization bypass in linked survey (IDOR) news IDOR | Vulnerability report on SurveyKing 1.12.0–1.13.2 detailing an authorization bypass in the linked survey feature. This flaw allows authenticated attackers to perform Insecure Direct Object Reference (IDOR) attacks by manipulating the `linkSurveyId`, enabling unauthorized reading, rewriting, or creation of responses in other users' surveys via the `loadLinkResult` and `updateLinkSurveyAnswer` functions. |
| 2026-11-14 NEW 2026 | The Green Agent POV: Formulating the Fix for an Exposed Container with Sensitive Data Access intermediate 7 min read Secrets | Tool that formulates remediation plans for exposed containers, detailing investigation into a critical issue involving a publicly exposed container with CVE-2026-111497, an insecure Kubernetes cluster, an overprivileged IAM role, and sensitive data in S3 buckets. It validates exposure, assesses exploitability, evaluates cloud identity and data access, and traces code-to-cloud lineage to identify owners and generate actionable fix and mitigation strategies without disrupting production. → wiz.io |
| 2026-11-14 NEW 2026 | OpenEMR 8.5.0 insecure direct object reference news IDOR | OpenEMR version 8.5.0 is vulnerable to an insecure direct object reference (IDOR) flaw. This vulnerability could allow unauthorized access to sensitive patient data. The issue stems from improper access control within the software, potentially enabling attackers to view or modify records they should not have permission to access. This highlights a critical security weakness that needs to be addressed by upgrading to a patched version of OpenEMR. |
| 2026-11-14 NEW 2026 | Omnispace Agora Project = 26.10.0 IDOR news IDOR | Library advisory detailing an Insecure Direct Object Reference (IDOR) in Omnispace Agora Project versions prior to 26.10.0. An authenticated attacker can exploit this vulnerability by crafting a `reloadMailTypeId` parameter for the `Ctrl::getCurObj()` function in `CtrlMail.php`. This bypasses the `readRight()` ownership check, enabling unauthorized access and exfiltration of other users' private mail content. |
| 2026-11-14 NEW 2026 | AcyMailing: subscriber identity not bound to the record (IDOR) news IDOR | A security vulnerability in the AcyMailing Joomla/WordPress extension, specifically an Insecure Direct Object Reference (IDOR), has been identified. This bug allows attackers to potentially access or manipulate subscriber data by not properly binding subscriber identity to their records. This could lead to unauthorized access to sensitive user information. |
| 2026-11-14 NEW 2026 | NocoDB 2026.09.0 insecure direct object reference news API Sec IDOR | NocoDB versions prior to 2026.09.0 have a vulnerability related to insecure direct object references. This flaw could potentially allow unauthorized access to data or resources within the application. Users are strongly advised to upgrade to version 2026.09.0 or later to patch this security weakness. |
| 2026-11-14 NEW 2026 | Dolibarr 24.0.2 insecure direct object reference (IDOR) news IDOR | Library for identifying Insecure Direct Object References (IDORs) in applications. This advisory details a vulnerability in Dolibarr versions prior to 24.0.2, specifically within the REST Documents API of the ticket module. The flaw allows authenticated API users to access ticket attachments from other companies by bypassing a company-scope check. Attackers with ticket read permissions can exploit this by enumerating predictable ticket identifiers and accessing sensitive attachments like invoices and contracts belonging to third parties. |
| 2026-11-13 NEW 2026 | NvRoot (CVE-2026-47591) where in neocloud multi-tenant GPU environments, rent = root. Essentially it's a dirty page cache LPE using GPUs as catalyzer advanced 6 min read RCE | Library 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. |
| 2026-11-13 NEW 2026 | Inside Cirro: Enumeration as a Restricted Guest intermediate 10 min read API Sec | Library that adds support for enumerating Microsoft Entra ID applications and service principals as a restricted guest user. This functionality is achieved by traversing known application IDs using HTTP GET requests, bypassing the typical Microsoft Graph API enumeration limitations for such accounts, and was previously difficult for tools like AzureHound and ROADtools. → bishopfox.com |
| 2026-11-13 2026 | I Turned a Rigid, Hardcoded Role System into a Dynamic RBAC Architecture, Without Breaking a Single… intermediate API Sec | This article details the process of transforming a rigid, hardcoded role system into a dynamic Role-Based Access Control (RBAC) architecture. The author achieved this by implementing permission slugs, a role-mapping layer, and backend-enforced checks. This approach allowed for a scalable authorization system without disrupting existing functionality, ensuring a smooth transition from the previous static model. |
| 2026-11-13 2026 | Drupal GraphQL Core Schema critical improper authorization: password change account takeover (SA-CONTRIB-2026-316) news AuthN GraphQL | Advisory for SA-CONTRIB-2026-316 on Drupal GraphQL Core Schema details an improper authorization vulnerability. This flaw allows users who can view other accounts to change their passwords via the GraphQL API, potentially leading to account takeover, including administrator accounts. The vulnerability is mitigated if the User Login schema extension is not enabled. An upgrade to GraphQL Core 1.0.29 or disabling the User Login extension is recommended. |
| 2026-11-13 2026 | Candlepin ConsumerResource.setupOwner missing authorization (IDOR) news IDOR | Writeup of GHSA-jff5-xmhg-5fjr detailing an IDOR vulnerability in Candlepin's ConsumerResource.setupOwner function. This flaw allows a low-privileged attacker with a valid consumer certificate to register a new consumer in a different organization, subsequently viewing subscription pools and attaching entitlements. The vulnerability stems from an incomplete authorization check when callers authenticate via identity certificates, bypassing user permission checks. |
Frequently Asked Questions
- What is broken access control?
- Broken access control occurs when an application fails to enforce restrictions on what authenticated users are allowed to do. This can lead to unauthorized access to other users' data, privilege escalation to admin roles, or performing actions outside the user's intended permissions — such as modifying or deleting resources they should not have access to.
- What is the difference between authentication and authorization?
- Authentication verifies identity (who are you?), while authorization determines permissions (what can you do?). A user can be properly authenticated but still access resources they shouldn't if authorization checks are missing or flawed. Many critical vulnerabilities arise from this distinction being overlooked.
- How do you test for authorization vulnerabilities?
- Test by accessing resources with different user roles, manipulating tokens or session cookies, changing IDs in API requests, and attempting to reach admin endpoints as a regular user. Tools like Autorize (Burp extension) automate this by replaying requests with different session tokens to detect missing authorization checks.
Weekly AppSec Digest
Get new resources delivered every Monday.