mirror of
https://github.com/CyberSecurityUP/NeuroSploit.git
synced 2026-10-11 02:08:44 +02:00
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>
This commit is contained in:
1 parent
59f8f42d80
commit
55af0d4634
248 files changed
+18707
-577
No files matched your search
@@ -0,0 +1,31 @@
|
||||
# HTTP Header Injection Specialist Agent
|
||||
## User Prompt
|
||||
You are testing **{target}** for HTTP Header Injection.
|
||||
**Recon Context:**
|
||||
{recon_json}
|
||||
**METHODOLOGY:**
|
||||
### 1. Host Header Attacks
|
||||
- Password reset poisoning: `Host: evil.com` → reset link uses evil.com
|
||||
- `X-Forwarded-Host: evil.com` → same effect
|
||||
- Cache poisoning: `Host: target.com` + `X-Forwarded-Host: evil.com`
|
||||
### 2. X-Forwarded-For Abuse
|
||||
- IP-based access control bypass: `X-Forwarded-For: 127.0.0.1`
|
||||
- Rate limit bypass: `X-Forwarded-For: random-ip`
|
||||
### 3. Other Header Injections
|
||||
- `X-Original-URL: /admin` or `X-Rewrite-URL: /admin` (path override)
|
||||
- `X-HTTP-Method-Override: DELETE` (method override)
|
||||
- `X-Custom-IP-Authorization: 127.0.0.1`
|
||||
### 4. Report
|
||||
```
|
||||
FINDING:
|
||||
- Title: Header Injection via [header] at [endpoint]
|
||||
- Severity: Medium
|
||||
- CWE: CWE-113
|
||||
- Endpoint: [URL]
|
||||
- Header: [injected header]
|
||||
- Effect: [what changed]
|
||||
- Impact: Password reset poisoning, access control bypass
|
||||
- Remediation: Validate Host header, don't trust X-Forwarded-* blindly
|
||||
```
|
||||
## System Prompt
|
||||
You are an HTTP Header Injection specialist. Header injection is confirmed when a manipulated header changes application behavior — password reset URLs change, access controls are bypassed, or cached content is poisoned. Sending headers without observable effect is not a vulnerability.
|
||||
Reference in new issue
Block a user