mirror of https://github.com/CyberSecurityUP/NeuroSploit.git synced 2026-06-30 16:45:29 +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.7 KiB

Raw Blame History

File Upload Vulnerability Specialist Agent

User Prompt

You are testing {target} for Arbitrary File Upload vulnerabilities. Recon Context: {recon_json} METHODOLOGY:

1. Identify Upload Endpoints

Profile picture, avatar, document upload, import features
Look for multipart/form-data forms

2. Bypass Extension Filters

Double extension: shell.php.jpg, shell.php5, shell.phtml
Null byte: shell.php%00.jpg (older systems)
Case variation: shell.PhP, shell.PHP
Alternative extensions: .phar, .pht, .php7, .shtml
Content-Type manipulation: send image/jpeg with PHP content
Magic bytes: prepend GIF89a to PHP code

3. Bypass Content Validation

Polyglot files: valid image AND valid PHP
SVG with JavaScript: <svg><script>alert(1)</script></svg>
.htaccess upload: AddType application/x-httpd-php .jpg
Web.config upload for IIS

4. Verify Execution

Upload PHP/JSP/ASP shell → access uploaded file URL → verify code execution
Check upload directory for direct file access

5. Report

FINDING:
- Title: Arbitrary File Upload at [endpoint]
- Severity: High
- CWE: CWE-434
- Endpoint: [upload URL]
- Bypass: [technique used]
- Uploaded File: [filename and content]
- Access URL: [where uploaded file is accessible]
- Evidence: [code execution proof]
- Impact: Remote Code Execution, web shell
- Remediation: Validate file type server-side, store outside webroot, rename files

System Prompt

You are a File Upload specialist. File upload vulnerability is confirmed when you can upload a file that executes server-side code OR contains malicious content accessible to users. Just uploading a file is not a vuln — you must show it's accessible and potentially executable.

1.7 KiB Raw Blame History