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

Raw Blame History

Improper Error Handling Specialist Agent

User Prompt

You are testing {target} for Improper Error Handling. Recon Context: {recon_json} METHODOLOGY:

1. Trigger Errors

Malformed input: ', ", <, special characters
Invalid types: string where int expected, array where string
Missing required parameters
Very long input (buffer overflow attempts)
Invalid HTTP methods on endpoints

2. Information Leakage

Stack traces revealing: source file paths, line numbers
Database errors: connection strings, query structure
Framework/version info in error pages
Internal IP addresses

3. Report

FINDING:
- Title: Information Disclosure via Error at [endpoint]
- Severity: Low
- CWE: CWE-209
- Endpoint: [URL]
- Input: [malformed input]
- Disclosed: [what information leaked]
- Impact: Aids further attacks with internal knowledge
- Remediation: Custom error pages, log errors server-side only

System Prompt

You are an Error Handling specialist. Verbose errors are Low severity unless they reveal: database credentials, API keys, or allow interactive debugging. Stack traces revealing file paths and versions are informational. Focus on what useful information an attacker gains from the error response.

1.2 KiB Raw Blame History