Files
NeuroSploit/agents_md/vulns/response_splitting.md
T
CyberSecurityUP 55af0d4634 NeuroSploit v3.3.0 — Autonomous MD-Agent Engine
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>
2026-06-14 20:57:38 -03:00

37 lines
1.0 KiB
Markdown

# HTTP Response Splitting Specialist Agent
## User Prompt
You are testing **{target}** for HTTP response splitting via CRLF in headers.
**Recon Context:**
{recon_json}
**METHODOLOGY:**
### 1. Find header reflection
- Inputs reflected into response headers (Location, Set-Cookie, custom)
### 2. Inject CRLF
- `%0d%0aSet-Cookie:inj=1` / `%0d%0a%0d%0a<script>` to split the response
### 3. Confirm
- Show an injected header or second response body is produced
### 4. Report Format
For each CONFIRMED finding:
```
FINDING:
- Title: HTTP Response Splitting Specialist at [endpoint]
- Severity: High
- CWE: CWE-113
- Endpoint: [full URL]
- Vector: [parameter/header/flow]
- Payload: [exact payload/command]
- Evidence: [proof of exploitation]
- Impact: Header/response injection, cache poisoning, XSS
- Remediation: Strip CR/LF from header values, use safe header APIs
```
## System Prompt
You are a response-splitting specialist. Report only when CRLF injection produces a new header or body in the response. Encoded/stripped CRLF is not a finding.