Skip to main content

LeakRadar Logo

LeakRadar

Open-Core API Security Engine for Automated BOLA & IDOR Vulnerability Scanning

CI Pipeline Python Version License


⚡ Overview

LeakRadar is an open-core DAST scanner designed specifically for REST APIs. It detects Broken Object Level Authorization (BOLA / IDOR) defects, token privilege escalation, and exposed secrets with near-zero false positives using a cross-token pairwise heuristic matrix algorithm.

                        LeakRadar Vulnerability Summary                        
+-----------------------------------------------------------------------------+
| Endpoint             | Params               | Status | Overlap | Confidence |
|----------------------+----------------------+--------+---------+------------|
| /api/v1/patients/{p} | {"patient_id":       |  200   |  100.0% |    HIGH    |
|                      | "REC-9901"}          |        |         |            |
+-----------------------------------------------------------------------------+
[3/3] Generating redacted proof-of-concept reports...
Saved Markdown PoC: demo_findings/bola_api_v1_patients_patient_id_records.md
+--------- Scan Finished ---------+
| Scan Completed Successfully!    |
| Total Findings: 1               |
+---------------------------------+

🌟 Key Features

  • 3-Baseline Volatility Diffing: Prunes volatile fields (timestamps, nonces, session IDs) across triple User A baselines before cross-token evaluation.
  • JWT Claim Harvesting: Automatically parses bearer token claims (sub, user_id, email) to seed parameterized endpoints (/api/v1/patients/{patient_id}).
  • Cross-Token Replay Matrix: Replays harvested endpoints using User B's identity, evaluating leaf-level scalar field overlap, ID echoing, and ownership matches.
  • Payload Secret Scanner: Integrated Shannon entropy analysis ($\ge 4.5$) and regex rules for AWS keys, Stripe tokens, private keys, and API credentials.
  • Redacted PoC Deliverables: Exports Markdown & Executive PDF reports with auto-redacted authorization tokens and proof steps.

🚀 Quick Start

Installation

git clone https://github.com/Ajmax76/leakradar.git
cd leakradar
pip install -e .

Run BOLA Vulnerability Scan

leakradar scan \
  --base-url "http://127.0.0.1:8000" \
  --spec "http://127.0.0.1:8000/openapi.json" \
  --token-a "Bearer eyJhbGci..." \
  --token-b "Bearer eyJhbGci..." \
  --output "./findings"

📖 Step-by-Step Usage Guide

Step 1: Obtain 2 User Tokens

To detect BOLA / IDOR defects, LeakRadar tests if one user can access another user's private data. You need two authorization tokens:

  • Token A (--token-a) [VICTIM]: The Bearer token for User A (e.g. Dr. Sarah Jenkins). LeakRadar uses this token to fetch baseline responses and discover resource IDs (like patient_id: REC-9901).
  • Token B (--token-b) [ATTACKER]: The Bearer token for User B (e.g. Alex Miller). LeakRadar replays User A's requests using User B's token to check if User B is improperly granted access.

Step 2: Run the Scan Command

Execute leakradar scan against your target API server and OpenAPI specification.


🛠️ Command Parameter Breakdown

Parameter Required / Optional Description Example
--base-url Required The root HTTP/HTTPS address of your target API server. http://127.0.0.1:8000
--spec Required The URL or local file path to the target's OpenAPI 3.0 specification (openapi.json or swagger.json). LeakRadar uses this to map all endpoints and parameter schemas. http://127.0.0.1:8000/openapi.json
--token-a Required Authorization Bearer token for User A (Victim). Used to establish legitimate baseline responses and harvest valid resource identifiers. "Bearer eyJhbGci..."
--token-b Required Authorization Bearer token for User B (Attacker). Replays requests against User A's resources to verify authorization checks. "Bearer eyJhbGci..."
--output Optional Directory path where vulnerability reports and cURL PoC files will be saved. Default is ./findings. ./findings
--allow-internal-spec Optional Flag to allow scanning target specs hosted on internal/local IP addresses (127.0.0.1, localhost). --allow-internal-spec
--allow-destructive Optional Enables testing of state-changing HTTP methods (POST, PUT, DELETE). By default, LeakRadar runs in Safe Mode (GET/HEAD only). --allow-destructive
--format Optional Report export format (markdown, pdf, all). Default is markdown. --format markdown

📊 Feature Matrix (Community vs Pro Auditor vs Enterprise)

Feature Community Edition (Free) Pro Auditor ($30/mo) Enterprise / Custom
BOLA / IDOR Detection Engine ✅ Full Engine ✅ Full Engine ✅ Full Engine
Redacted Markdown PoC Export ✅ Included ✅ Included ✅ Included
Scan Speed Mode ⏱️ 1.5s Throttled ⚡ Maximum Speed (0s delay) ⚡ Unlimited Parallel Threads
Executive PDF Reports ❌ Locked 📄 Full PDF Deliverables 📄 Full PDF Deliverables
Custom White-Label Branding ❌ Locked 🏢 Custom Logo & Company 🏢 Custom Logo & Company
Commercial Audit Rights Non-Commercial Only ✅ Solo Security Auditors 🏢 Organization-Wide License

🏢 Enterprise & Custom Licensing

For organizations requiring custom capabilities, the Enterprise Tier provides:

  • Custom Auth Adapters: Tailored support for complex authentication flows (Okta SSO, mTLS, custom header handshakes, dynamic CSRF tokens).
  • Air-Gapped & On-Prem Deployment: Private execution within isolated corporate networks without external licensing checks.
  • Organization-Wide Rights: Unlimited security team members and automated CI/CD pipeline scanning rights.
  • Bespoke Compliance Deliverables: Customized executive PDF reports mapped to SOC2, ISO27001, or HIPAA requirements.

🧪 Local Demo Target

A vulnerable BOLA REST API testbed is provided in demo_target/app.py. It includes:

  • Authentication Endpoint (/api/v1/auth/login): Issues standard 3-part Bearer JWT tokens for two distinct users (user_101 and user_102).
  • Two Vulnerable BOLA Endpoints: GET /api/v1/patients/{patient_id}/records and GET /api/v1/users/{user_id}/profile (both handlers decode the caller's JWT identity, but fail to verify resource ownership).
  • One Secured Control Endpoint: GET /api/v1/users/{user_id}/billing (decodes caller identity AND enforces ownership checks, returning 403 Forbidden on mismatch to verify false positive suppression).
# Start the demo target REST API
python demo_target/app.py

📄 License & Commercial Terms

The core open-source codebase is licensed under the verbatim PolyForm Noncommercial License 1.0.0.

  • Non-Commercial Use: Free for security researchers, academic evaluation, and non-commercial vulnerability testing.
  • Commercial Use: Using LeakRadar for paid client security audits, managed security services (MSSP), or commercial products is governed by our Commercial Terms.

Note: Organizations deploying LeakRadar commercially should conduct formal legal review of commercial licensing agreements.

Metadata

Release files for leakradar-cli 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for leakradar-cli 0.2.0
File Size Uploaded Provenance Actions
leakradar_cli-0.2.0.tar.gz 36.7 kB Without provenance Details for leakradar_cli-0.2.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for leakradar-cli 0.2.0
File Interpreter ABI Platform Actions
leakradar_cli-0.2.0-py3-none-any.whl Python 3 none any Details for leakradar_cli-0.2.0-py3-none-any.whl

Total release size: 67.2 kB

Release files / leakradar_cli-0.2.0.tar.gz

Download URL leakradar_cli-0.2.0.tar.gz
Size 36.7 kB
Tags Source
SHA-256 checksum
How to use checksums
db800f50ce97e0be34de60f5647b80958bd204b3b94005fe7b76b545cfcc3cbf
BLAKE2b-256 checksum
How to use checksums
75e8ce13ed2c7f3db2cb6491490b3209f64640f345dc43732b73dd2b5c8e7195
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.10.21

Release files / leakradar_cli-0.2.0-py3-none-any.whl

Download URL leakradar_cli-0.2.0-py3-none-any.whl
Size 30.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
cd60ef1f0bf6ac8ffbd3819af8247c4f8c8c5ada6e9eaecfaaaa605c7f26aa02
BLAKE2b-256 checksum
How to use checksums
12629e4f3d3d401541c53bef61c3571e79d6167b7db6537fd217673809bb3850
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.10.21

Security for leakradar-cli 0.2.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.2.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page