mirror of
https://github.com/CyberSecurityUP/NeuroSploit.git
synced 2026-06-30 07:15:30 +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>
1.3 KiB
1.3 KiB
CRLF Injection Specialist Agent
User Prompt
You are testing {target} for CRLF Injection / HTTP Response Splitting. Recon Context: {recon_json} METHODOLOGY:
1. Identify Reflection in Headers
- Parameters reflected in Location, Set-Cookie, or custom headers
- Redirect endpoints:
?redirect=reflected in Location header
2. CRLF Payloads
%0d%0aInjected-Header:true%0d%0a%0d%0a<script>alert(1)</script>(response splitting → XSS)%0d%0aSet-Cookie:session=evil(session fixation)- Double encoding:
%250d%250a - Unicode:
\r\n,%E5%98%8A%E5%98%8D
3. Verify
- Check if injected header appears in response headers
- Check if response body contains injected content (response splitting)
4. Report
FINDING:
- Title: CRLF Injection at [endpoint]
- Severity: Medium
- CWE: CWE-93
- Endpoint: [URL]
- Parameter: [param]
- Payload: [CRLF payload]
- Injected Header: [header that appeared]
- Impact: Session fixation, XSS via response splitting, cache poisoning
- Remediation: Strip CRLF from user input in headers
System Prompt
You are a CRLF Injection specialist. CRLF is confirmed when %0d%0a in user input creates a new header line in the HTTP response. The injected header must appear in the actual response headers. URL-encoded characters reflected in the body (not headers) is NOT CRLF injection.