Operacao do smuggler no Khaos
O adapter Khaos executa smuggler com -t 5 --no-color contra um unico endpoint observado. Detecta diferencas de parsing CL.TE e TE.CL mas nao confirma explorabilidade.
Pre-condicoes obrigatorias
- Stage da task:
vulnouvalidation. - Endpoint: URL HTTP/1.1 observada e confirmada in-scope (HTTPS com terminacao TLS proxima).
- Estado do assessment:
executing_stage. - Hipotese de HTTP desync registrada antes de executar.
Fluxo correto de execucao
1. POST /assessments/{id}/operator/tasks/{taskId}/claim
{"owner": "<owner>", "lease_seconds": 180}
2. POST /assessments/{id}/operator/events
{"event": "action_proposed", "data": {
"action_id": "<uuid-novo>",
"task_id": "<taskId>",
"owner": "<owner>",
"tool_id": "smuggler",
"title": "smuggler HTTP desync probe: <endpoint>"
}}
3. POST /assessments/{id}/operator/events
{"event": "action_decision", "data": {
"action_id": "<mesmo-uuid>",
"task_id": "<taskId>",
"owner": "<owner>",
"tool_id": "smuggler",
"allowed": true
}}
4. POST /tools/smuggler/run
{"target_id": "<id>", "assessment_id": "<id>",
"endpoint_url": "<url>",
"execute": true, "confirm": true,
"action_id": "<mesmo-uuid>", "task_id": "<taskId>", "owner": "<owner>"}
O que o wrapper executa
Flags: -u <endpoint> -t 5 --no-color. Testa variantes CL.TE e TE.CL padrao da suite defparam.
Interpretar sem superafirmar
| Resultado | Interpretacao |
|---|---|
Issue Found / VULNERABLE |
Candidato de desync — confirmar diferencial completo |
No issues found |
Sem sinal nesta configuracao — nao exclui desync em outros caminhos |
| Timeout / erro de conexao | Endpoint nao alcancavel ou balanceador sem suporte a HTTP/1.1 |
Resultado positivo exige reproducao com dois perfis distintos (request de veneno + request de contrabando) antes de criar finding.