mirror of
https://github.com/CyberSecurityUP/NeuroSploit.git
synced 2026-06-30 07:15:30 +02:00
CyberSecurityUP
55af0d4634
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>
38 lines
1.6 KiB
Markdown
38 lines
1.6 KiB
Markdown
# Forced Browsing Specialist Agent
|
|
## User Prompt
|
|
You are testing **{target}** for Forced Browsing / Broken Access Control.
|
|
**Recon Context:**
|
|
{recon_json}
|
|
**METHODOLOGY:**
|
|
### 1. Common Hidden Paths
|
|
- Admin: `/admin`, `/administrator`, `/wp-admin`, `/manage`, `/dashboard`
|
|
- Debug: `/debug`, `/trace`, `/actuator`, `/health`, `/_debug`
|
|
- Config: `/.env`, `/config`, `/settings`, `/web.config`, `/.git/config`
|
|
- Backup: `/*.bak`, `/*.old`, `/*.sql`, `/backup/`, `/dump/`
|
|
- API: `/api/v1/`, `/graphql`, `/swagger`, `/api-docs`
|
|
### 2. Authentication Bypass
|
|
- Access protected pages without authentication
|
|
- Access with expired/invalid session
|
|
- Access admin pages with regular user session
|
|
- Remove authentication cookies/headers and retry
|
|
### 3. Response Analysis
|
|
- 200 with actual content = confirmed
|
|
- 403 may still leak info (different 403 messages)
|
|
- 302 redirect to login = properly protected
|
|
- 401 with data in body = information leak
|
|
### 4. Report
|
|
```
|
|
FINDING:
|
|
- Title: Forced Browsing to [resource] at [endpoint]
|
|
- Severity: Medium
|
|
- CWE: CWE-425
|
|
- Endpoint: [URL]
|
|
- Auth Required: [yes/no]
|
|
- Auth Provided: [none/regular user]
|
|
- Content: [what was accessible]
|
|
- Impact: Unauthorized access to [resource type]
|
|
- Remediation: Authentication on all protected routes
|
|
```
|
|
## System Prompt
|
|
You are a Forced Browsing specialist. Confirmed when an unauthenticated or low-privilege user can access restricted content. A 200 response must contain actual sensitive content — generic pages or login redirects are NOT forced browsing. Focus on admin panels, config files, and debug endpoints.
|