api-bola
Broken Object/Function Level Authorization in REST/JSON APIs (the #1 API risk). Load on any REST API with object ids in paths/bodies (/api/v1/users/123, /orders/{id}), Bearer auth, mobile-app backends, or admin vs user function separation. Signals: predictable ids, verbs that skip re-authorization,
v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 22 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/api-bolaWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package582dc1dc…682a39c1
582dc1dca3f7…1533682a39c12 files · 2.7 KBScanLowno findings
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/api/api-bola@ee0e0c5
On this page
When it applies
An API exposes objects (BOLA) or privileged functions (BFLA) and enforces authorization weakly. The API version of IDOR — but APIs multiply the surface (many endpoints, verbs, versions, and a mobile client that trusts the server less than the web UI does).
Why it works
APIs are stateless and object-centric; each endpoint must independently check "can this token act on this object/function?". Teams centralize authentication but scatter (or forget) authorization, and hide admin functions in the client instead of the server.
Method
- BOLA: with two tokens, request another user's object id on every endpoint & verb; also try guessing/incrementing ids and IDs leaked from list endpoints.
- BFLA: take an admin-only call (from JS, mobile, or docs) and replay it with a low-priv token; try method swaps (GET→PUT/DELETE) and hidden verbs the UI never issues.
- Version & shadow endpoints:
/api/v1/may lack fixes present in/v2/;/internal/,/debug/, Swagger/OpenAPI docs reveal ungoverned routes. - Automate with Burp Autorize (low-priv token as the "enforcement" session) to flag every request that succeeds when it shouldn't.
Gotchas
- 200 vs 403 is the tell, but some APIs return 200 with an empty body — diff the content.
- IDs as UUIDs still leak via list/search endpoints and other objects' relations.
- Rate-limit and WAF differ per API version — the vuln may only show on an older route.
Verify success
A low-privilege (or cross-tenant) token successfully reads/modifies an object or invokes a function reserved for another user/role.
References
OWASP API Security Top 10 (2023) API1/API5; PortSwigger access-control labs.
Files in this version
- detection.md2.8 KB
- SKILL.md2.3 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
The scan found nothing to flag in this version.
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | Nov 13, 2026 | ee0e0c5 | 582dc1dc | Signed | – |
More from NoorQureshi
All from this publisherMore in APIs, SaaS and identity
See the category- testing-for-sensitive-data-exposuremukul975/testing-for-sensitive-data-exposure5
- performing-jwt-none-algorithm-attackmukul975/performing-jwt-none-algorithm-attack5
- sharp-edgestrailofbits/sharp-edges4
- hydraaeondave/hydra4
- implementing-google-workspace-admin-securitymukul975/implementing-google-workspace-admin-security4
- implementing-api-security-posture-managementmukul975/implementing-api-security-posture-management4
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login