Operacao do cbh no Khaos
O cbh (Claude BugHunter CLI) executa um pipeline deterministico de 6 fases: recon, enumeration, auth, authorization, fuzzing e validation. Cada fase produz hipoteses priorizadas baseadas em padroes de relatorios HackerOne reais.
Pre-condicoes obrigatorias
- Stage da task:
recon,enumeration,vulnouvalidation. - Endpoint: URL do alvo in-scope; cbh aceita URLs com e sem path.
- Estado do assessment:
executing_stage. - O cbh e instalado via
khaos_install_toolantes do primeiro uso.
Fluxo correto de execucao
1. khaos_install_tool(tool_id="cbh") — aguardar job_id completed
2. POST /assessments/{id}/operator/tasks/{taskId}/claim
{"owner": "<owner>", "lease_seconds": 300}
3. POST /assessments/{id}/operator/events
{"event": "action_proposed", "data": {
"action_id": "<uuid-novo>",
"task_id": "<taskId>",
"owner": "<owner>",
"tool_id": "cbh",
"title": "cbh 6-phase scan: <target>"
}}
4. POST /assessments/{id}/operator/events
{"event": "action_decision", "data": {
"action_id": "<mesmo-uuid>",
"task_id": "<taskId>",
"owner": "<owner>",
"tool_id": "cbh",
"allowed": true
}}
5. POST /tools/cbh/run
{"target_id": "<id>", "assessment_id": "<id>",
"endpoint_url": "<url>",
"execute": true, "confirm": true,
"action_id": "<mesmo-uuid>", "task_id": "<taskId>", "owner": "<owner>"}
Interpretacao da saida
O cbh emite hipoteses por fase com nivel de confianca e referencia ao padrao HackerOne. Nao cria findings automaticamente.
| Nivel | Acao |
|---|---|
| HIGH confidence | Reproduzir com 3 execucoes independentes antes de criar finding |
| MEDIUM confidence | Investigar manualmente; usar khaos_http_request para confirmar |
| LOW confidence | Registrar como nota/hipotese; nao reportar sem evidencia adicional |
Limites do adapter
O adapter Python nao executa payloads destrutivos nem envia dados a endpoints terceiros. Fases de fuzzing usam canarios inertes. Para coverage de BOLA/IDOR, cbh requer dois perfis de auth configurados no assessment.