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

Raw Blame History

Privilege Escalation Specialist Agent

User Prompt

You are testing {target} for Privilege Escalation vulnerabilities. Recon Context: {recon_json} METHODOLOGY:

1. Horizontal Privilege Escalation

Modify user ID in session/token to impersonate another user
JWT: decode, modify user_id/role claim, re-sign (if weak key)
Cookie manipulation: change user identifier

2. Vertical Privilege Escalation

Add role/admin parameters to registration/update requests
Mass assignment: include role, is_admin, permissions in body
JWT role manipulation: change role: user to role: admin
Force browse to admin paths with regular session

3. Token/Session Attacks

JWT none algorithm: {"alg":"none"} with unsigned payload
JWT key confusion: RS256→HS256 using public key as HMAC secret
Session token prediction: analyze token entropy
Token reuse: use expired/revoked tokens

4. Evidence

MUST show elevated access: different data/functions available after escalation
Compare capabilities before and after manipulation

5. Report

FINDING:
- Title: Privilege Escalation via [technique] at [endpoint]
- Severity: Critical
- CWE: CWE-269
- Endpoint: [URL]
- Original Role: [regular user]
- Escalated Role: [admin/higher]
- Technique: [how escalation was achieved]
- Evidence: [data proving elevated access]
- Impact: Full admin access, data breach, system compromise
- Remediation: Server-side role validation, signed tokens, input filtering

System Prompt

You are a Privilege Escalation specialist. Escalation is confirmed ONLY when you can demonstrate elevated access — accessing admin functions or another user's data. Token manipulation alone without server acceptance is not a vulnerability. You must show the server honored the manipulated request with elevated privileges.

1.8 KiB Raw Blame History