convez.ai
MCP ServerSegurançaAvançado
momomuchu

Burp Wrapper (bp) — CLI para Burp Suite

momomuchu/burp-wrapper

Drive Burp Suite do CLI com fuzzing scriptável e saída JSON

Ver no GitHub
InicialPluginScore · de 0 a 100

Cliente Python totalmente tipado que controla Burp Suite via CLI, permitindo fuzzing multi-posição, capture de tráfego e scanning sem ficar preso à UI. Integra-se via extensão REST em Kotlin, herdando todo o contexto HTTP do Burp — ideal para bug-bounty hunters e agentes IA automarem testes de segurança.

Instalação

$npx convez-ai momomuchu/burp-wrapper

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
1
Forks
1
Acompanhando
0
Saúde
85%
Último commit
há 3 semanas
Versão
v2.0.0
Issues abertas
32
Contribuidores
1

Casos de uso

  • Fuzzing multi-posição automatizado sem throttling de Community
  • Automação de testes de segurança em pipelines CI/CD
  • Integração com agentes IA para reconhecimento e scanning
  • Detecção de auth-bypass, IDOR e CORS via probes integrados

Veredito

MCP server robusto e bem arquitetado para profissionais de segurança que precisam automatizar Burp Suite em scripts e orquestrações. Oferece controle fino via REST API, contornando limitações da Community — recomendado para quem trabalha com bug-bounty e pentesting em escala.

README

A tradução para o português deste README ainda está na fila.

bp

Release CI License: MIT Python 3.11+ Burp Suite

Drive Burp Suite from the command line. Mark any byte range, fuzz it fast, and get clean parsable output — through Burp's HTTP stack and project context.

A scriptable Burp Suite CLI and Intruder alternative for bug-bounty hunters and pentesters.

The reason to reach for bp over ffuf or Turbo Intruder: those are fast, but they run outside Burp — you lose its HTTP stack, upstream configuration, and project context. bp builds the attack client-side and sends every shot through Burp's Repeater (/repeater/send), not Burp's Intruder engine — so your fuzzing inherits all of that context in one scriptable command instead of a UI full of clicks. And because it rides Repeater, it sidesteps the deliberate rate-throttle that Burp Community applies to Intruder: multi-position, matrix-style fuzzing at full speed while staying inside the proxy you're already using.

It's two pieces:

  • bp — a fast, fully-typed Python CLI (the interface you'll use; also installed as burpctl).
  • burp-rest-extension — a Kotlin Burp extension that exposes Burp's Montoya API as a local REST API for bp to drive.
 you ──►  bp (CLI)  ──REST :8089──►  burp-rest-extension  ──Montoya──►  Burp Suite (Pro / Community)

Features

  • 💥 Flexible client-side fuzzing — mark any byte range (header:, cookie:, body:, query:, path:, raw offset:), multiple positions at once, and all four attack types (sniper, battering-ram, pitchfork, cluster-bomb) with built-in anomaly detection. Not throttled on Community.
  • 🎯 Truthful Burp control surface — proxy history, Repeater, Scanner, target/scope, decoder, Collaborator, sitemap, and sessions; operations absent from pinned Montoya return typed UNSUPPORTED, never successful no-ops.
  • 🔎 Security checks — built-in probes for auth-bypass, IDOR, CORS, and security headers; exit code 5 only on confirmed classifier findings, while anomalies remain triage observations.
  • 📒 Run Ledger — every bp-to-extension operation is recorded locally with sha256 fingerprints only (never raw bodies), and secret redaction is on by default; it is not a curl/xh/browser traffic log.
  • 🧰 Works on Community too — only collaborator and scan start need Pro (they exit 4 with a clear message); everything else runs on Community.
  • 🔩 Scriptable & automation-friendly — --format json emits NDJSON (one record per line); stable exit codes; no interactive prompts. That also makes it easy to drive from scripts or AI agents.
  • ✅ Spec-driven & tested — extensive hermetic Python and Kotlin regression suites, strict typing/linting, OpenAPI validation, package smoke tests, and CI on every push.

How it compares

Where bp fits next to the tools you already reach for when Burp's Intruder is too slow or too clicky:

Uses Burp's HTTP stackAll 4 attack typesFast on CommunityShell-scriptable CLI
bp✅✅ sniper · ram · pitchfork · cluster-bomb✅ (fires via Repeater)✅
Burp Intruder (Pro)✅✅✅❌ GUI only
Burp Intruder (Community)✅✅❌ deliberately throttled❌ GUI only
Turbo Intruder✅ (extension)⚠️ Python-scripted✅ very fast⚠️ in-Burp scripting
ffuf❌ outside Burp✅✅✅

Honest take: ffuf and Turbo Intruder win on raw throughput. bp wins when you want a one-line, scriptable command that uses Burp's HTTP stack and project context — and full-speed multi-position fuzzing on Community without the GUI throttle.

Quickstart

Requirements: Burp Suite (Pro or Community) · JDK 17+ (to build the extension) · Python 3.11+ (for bp).

1. Build & load the extension

./gradlew shadowJar     # → build/libs/burp-rest-extension.jar

In Burp: Extensions → Add → Extension type: Java → select the JAR. The REST server auto-starts — look for Server started on http://127.0.0.1:8089 in the extension's Output tab.

Prefer not to build? Grab the prebuilt jar from the latest release.

2. Install & use bp

cd bp && uv tool install .          # or: pipx install .   (installs `bp` + `burpctl` alias)

bp health                                       # is the extension up?
bp proxy --host target.example --limit 20       # captured history → request IDs

# fuzz two positions at once, cluster-bomb, show only anomalies:
bp fuzz 42 --pos 'header:X-Forwarded-For' --payloads X-Forwarded-For=ssrf.txt \
           --pos 'cookie:role'            --payloads role=privesc.txt \
           --type cluster-bomb --anomalous-only

bp check idor 'https://target/api/user?id=1' --param id --own 1 --target 2   # exits 5 if vulnerable

Output: default is a human table; add --format json (NDJSON), raw, or quiet for scripts and agents. Global flags (--url / --format / --fields) work in either position. burpctl is a drop-in alias for bp.

👉 Full command reference: bp/README.md.

Repository layout

PathWhat
bp/The bp CLI (Python) — README · CHANGELOG
src/main/kotlin/com/burprest/The Burp REST extension (Kotlin / Ktor / Montoya)
docs/Source-grounded contracts: SPEC · CLI grammar · OUTPUT · ALGORITHMS · ADRs

The REST surface is 13 route groups / 69 endpoints, all source-verified in docs/SPEC.md; every response is {success, data, error}.

Build & test

./gradlew test                                              # Kotlin extension
cd bp && uv run pytest -q && uv run mypy --strict src && uv run ruff check src tests   # 440+ Python tests

FAQ

Does it work on Burp Suite Community? Yes. Every command runs on Community except collaborator and starting an active scan — those need Pro and exit 4 with a clear message. Fuzzing in particular is not subject to Community's Intruder throttle, because bp fires each request through Burp's Repeater.

How is this different from ffuf? ffuf is a great standalone fuzzer, but it runs outside Burp — it doesn't use Burp's HTTP stack, upstream configuration, or project context. bp drives Burp itself. A replay preserves the captured request's cookies and headers; Burp target scope is classification metadata, not a forwarding block. Use ffuf for raw speed on unauthenticated endpoints; use bp when you want Burp's configured HTTP stack and captured request as the experiment base.

Do I need Burp Suite Professional? No, for almost everything. Only Collaborator (out-of-band payloads) and starting an active scan require Pro. Proxy history, Repeater, fuzzing, scope, decoder, sitemap, and the IDOR/CORS/auth-bypass checks all work on Community.

Can I drive it from a script or an AI agent? Yes — --format json emits NDJSON (one record per line), exit codes are stable and documented, and there are no interactive prompts. That makes it easy to wire into CI, shell pipelines, or an agent.

Is bp the same as burpctl? Yes. bp is the primary command (short, one token); burpctl is an installed alias — identical behaviour.

Contributing

Issues and PRs welcome — bp is spec-driven and test-first. Start with CONTRIBUTING.md (disciplines, dev setup, Definition of Done), see the ROADMAP for what's planned, and report vulnerabilities privately per SECURITY.md.

⚠️ Authorized use only. This drives a security proxy — use it solely against systems you own or are explicitly permitted to test.

License

MIT

Ver o original no GitHub

Bom para

Relacionados