Back to catalog
Static reviewDevelopment

Skill dossier

testing-api-for-broken-object-level-authorization

Source declaration

Tests REST and GraphQL APIs for Broken Object Level Authorization (BOLA/IDOR, OWASP API1:2023) by intercepting API calls, identifying object ID parameters (numeric IDs, UUIDs, slugs), and systematically substituting IDs belonging to other users to check whether the server enforces per-object authorization. Use when asked to test BOLA or IDOR in an API, verify object-level authorization, or assess an API for access control bypass.

The author's original description, preserved in English. It describes intent, not verified performance.

Tests REST and GraphQL APIs for Broken Object Level Authorization (BOLA/IDOR, OWASP API1:2023) by intercepting API calls, identifying object ID parameters (numeric IDs, UUIDs, slugs), and systematically substituting IDs belonging to other users to check whether the server enforces per-object authorization. Use when asked to test BOLA or IDOR in an API, verify object-level authorization, or assess an API for access control bypass.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Tests REST and GraphQL APIs for Broken Object Level Authorization (BOLA/IDOR, OWASP API1:2023) by intercepting API calls, identifying object ID parameters (numeric IDs, UUIDs, slugs), and systematically substituting IDs belonging to other users to check whether the server enforces per-object authorization. Use when asked to test BOLA or IDOR in an API, verify object-level authorization, or assess an API for access control bypass. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/testing-api-for-broken-object-level-authorization/SKILL.md:L57]
  • Step 1: API Endpoint Discovery and Object ID Mapping [Source statement; provisional, not tested. Evidence: skills/testing-api-for-broken-object-level-authorization/SKILL.md:L59]
  • Step 2: Baseline Request Capture with Authenticated User [Source statement; provisional, not tested. Evidence: skills/testing-api-for-broken-object-level-authorization/SKILL.md:L98]
  • Step 3: BOLA Testing - Horizontal Privilege Escalation [Source statement; provisional, not tested. Evidence: skills/testing-api-for-broken-object-level-authorization/SKILL.md:L133]
  • Step 4: Advanced BOLA Techniques [Source statement; provisional, not tested. Evidence: skills/testing-api-for-broken-object-level-authorization/SKILL.md:L194]
  • Step 5: Automated BOLA Detection with Autorize (Burp Suite) [Source statement; provisional, not tested. Evidence: skills/testing-api-for-broken-object-level-authorization/SKILL.md:L251]
  • Step 6: GraphQL BOLA Testing [Source statement; provisional, not tested. Evidence: skills/testing-api-for-broken-object-level-authorization/SKILL.md:L270]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/testing-api-for-broken-object-level-authorization/SKILL.md:L1-L34]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
36.7 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/testing-api-for-broken-object-level-authorization/LICENSEOther11 KB
skills/testing-api-for-broken-object-level-authorization/references/api-reference.mdReference1.8 KB
skills/testing-api-for-broken-object-level-authorization/scripts/agent.pyScript8.2 KB
skills/testing-api-for-broken-object-level-authorization/SKILL.mdInstruction15.8 KB

SKILL.md frontmatter

{
  "name": "testing-api-for-broken-object-level-authorization",
  "description": "Tests REST and GraphQL APIs for Broken Object Level Authorization (BOLA/IDOR, OWASP API1:2023) by intercepting API calls, identifying object ID parameters (numeric IDs, UUIDs, slugs), and systematically substituting IDs belonging to other users to check whether the server enforces per-object authorization. Use when asked to test BOLA or IDOR in an API, verify object-level authorization, or assess an API for access control bypass.\n",
  "domain": "cybersecurity",
  "subdomain": "api-security",
  "tags": [
    "api-security",
    "owasp",
    "bola",
    "idor",
    "authorization",
    "rest-security"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.PS-01",
    "ID.RA-01",
    "PR.DS-10",
    "DE.CM-01"
  ],
  "mitre_attack": [
    "T1190",
    "T1059.007",
    "T1552.001",
    "T1027",
    "T1070"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: API Endpoint Discovery and Object ID Mapping

    Source-described action candidate under “Step 1: API Endpoint Discovery and Object ID Mapping”; not verified execution.

  4. 04
    Action

    Browse the application as User A, exercising all features that involve data creation and retrieval

    Source-described action candidate under “Step 1: API Endpoint Discovery and Object ID Mapping”; not verified execution.

  5. 05
    Action

    In Burp, go to Target > Site Map and filter for API paths (e.g., `/api/v1/`, `/graphql`)

    Source-described action candidate under “Step 1: API Endpoint Discovery and Object ID Mapping”; not verified execution.

  6. 06
    Action

    Look for patterns: `/api/v1/users/{id}`, `/api/v1/orders/{orderid}`, `/api/v1/documents/{docuuid}`

    Source-described action candidate under “Step 1: API Endpoint Discovery and Object ID Mapping”; not verified execution.

Inspect all extracted workflow candidates (38 candidate steps)
  1. 07
    Action

    Note the object ID format: sequential integers (predictable), UUIDs (less predictable), or encoded values

    Source-described action candidate under “Step 1: API Endpoint Discovery and Object ID Mapping”; not verified execution.

  2. 08
    Action

    Step 2: Baseline Request Capture with Authenticated User

    Source-described action candidate under “Step 2: Baseline Request Capture with Authenticated User”; not verified execution.

  3. 09
    Action

    Step 3: BOLA Testing - Horizontal Privilege Escalation

    Source-described action candidate under “Step 3: BOLA Testing - Horizontal Privilege Escalation”; not verified execution.

  4. 10
    Action

    Step 4: Advanced BOLA Techniques

    Source-described action candidate under “Step 4: Advanced BOLA Techniques”; not verified execution.

  5. 11
    Action

    Step 5: Automated BOLA Detection with Autorize (Burp Suite)

    Source-described action candidate under “Step 5: Automated BOLA Detection with Autorize (Burp Suite)”; not verified execution.

  6. 12
    Action

    Install Autorize from the BApp Store in Burp Suite Professional

    Source-described action candidate under “Step 5: Automated BOLA Detection with Autorize (Burp Suite)”; not verified execution.

  7. 13
    Action

    In the Autorize tab, paste User B's authentication cookie or header

    Source-described action candidate under “Step 5: Automated BOLA Detection with Autorize (Burp Suite)”; not verified execution.

  8. 14
    Action

    Configure the interception filters:

    Source-described action candidate under “Step 5: Automated BOLA Detection with Autorize (Burp Suite)”; not verified execution.

  9. 15
    Action

    Include: `.\/api\/.` (only API paths)

    Source-described action candidate under “Step 5: Automated BOLA Detection with Autorize (Burp Suite)”; not verified execution.

  10. 16
    Action

    Exclude: `.\.(js|css|png|jpg)$` (skip static assets)

    Source-described action candidate under “Step 5: Automated BOLA Detection with Autorize (Burp Suite)”; not verified execution.

  11. 17
    Action

    Set the enforcement detector:

    Source-described action candidate under “Step 5: Automated BOLA Detection with Autorize (Burp Suite)”; not verified execution.

  12. 18
    Action

    Add conditions where response length or status code differs between User A and User B

    Source-described action candidate under “Step 5: Automated BOLA Detection with Autorize (Burp Suite)”; not verified execution.

  13. 19
    Decision

    Mark as "enforced" if User A gets 403/401 for User B's resources

    Source-described decision candidate under “Step 5: Automated BOLA Detection with Autorize (Burp Suite)”; not verified execution.

  14. 20
    Decision

    Mark as "bypassed" if User A gets 200 with User B's data

    Source-described decision candidate under “Step 5: Automated BOLA Detection with Autorize (Burp Suite)”; not verified execution.

  15. 21
    Action

    Browse the application as User A; Autorize automatically replays each request with User B's token

    Source-described action candidate under “Step 5: Automated BOLA Detection with Autorize (Burp Suite)”; not verified execution.

  16. 22
    Action

    Review the Autorize results table:

    Source-described action candidate under “Step 5: Automated BOLA Detection with Autorize (Burp Suite)”; not verified execution.

  17. 23
    Action

    Green = Authorization enforced (secure)

    Source-described action candidate under “Step 5: Automated BOLA Detection with Autorize (Burp Suite)”; not verified execution.

  18. 24
    Action

    Red = Authorization bypassed (BOLA vulnerability)

    Source-described action candidate under “Step 5: Automated BOLA Detection with Autorize (Burp Suite)”; not verified execution.

  19. 25
    Action

    Orange = Needs manual review (ambiguous response)

    Source-described action candidate under “Step 5: Automated BOLA Detection with Autorize (Burp Suite)”; not verified execution.

  20. 26
    Action

    Step 6: GraphQL BOLA Testing

    Source-described action candidate under “Step 6: GraphQL BOLA Testing”; not verified execution.

  21. 27
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  22. 28
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  23. 29
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  24. 30
    Action

    Map all endpoints from the Swagger spec at `/api/docs`: identify 47 endpoints, 23 of which take object IDs

    Source-described action candidate under “Scenario: E-Commerce API BOLA Assessment”; not verified execution.

  25. 31
    Action

    Capture User A's requests for their own resources: profile, orders, addresses, payment methods, wishlist

    Source-described action candidate under “Scenario: E-Commerce API BOLA Assessment”; not verified execution.

  26. 32
    Action

    Replace User A's object IDs with User B's IDs systematically across all 23 endpoints

    Source-described action candidate under “Scenario: E-Commerce API BOLA Assessment”; not verified execution.

  27. 33
    Input

    Find that `GET /api/v1/orders/{id}` returns any order regardless of ownership (BOLA on read)

    Source-described input candidate under “Scenario: E-Commerce API BOLA Assessment”; not verified execution.

  28. 34
    Output

    Find that `PATCH /api/v1/addresses/{id}` allows modifying any user's address (BOLA on write)

    Source-described output candidate under “Scenario: E-Commerce API BOLA Assessment”; not verified execution.

  29. 35
    Action

    Find that `GET /api/v1/users/{id}/payment-methods` leaks payment card last-four digits for any user

    Source-described action candidate under “Scenario: E-Commerce API BOLA Assessment”; not verified execution.

  30. 36
    Output

    Test batch endpoint `POST /api/v1/orders/export` - accepts array of order IDs and exports all without ownership check

    Source-described output candidate under “Scenario: E-Commerce API BOLA Assessment”; not verified execution.

  31. 37
    Action

    Verify that `DELETE /api/v1/orders/{id}` correctly returns 403 for non-owned orders (authorization enforced)

    Source-described action candidate under “Scenario: E-Commerce API BOLA Assessment”; not verified execution.

  32. 38
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

33 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

21 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 21 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

11 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 11 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Downloaded content may be executed

This line combines retrieval and execution. Such patterns can run mutable remote code. Review pinning, integrity checks, and isolation; the analyzer performed no download or execution. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/testing-api-for-broken-object-level-authorization/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/testing-api-for-broken-object-level-authorization/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/testing-api-for-broken-object-level-authorization
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.