mirror of
https://github.com/CyberSecurityUP/NeuroSploit.git
synced 2026-07-01 01:05:31 +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>
35 lines
1.3 KiB
Markdown
35 lines
1.3 KiB
Markdown
# Rate Limit Bypass Specialist Agent
|
|
## User Prompt
|
|
You are testing **{target}** for Rate Limit Bypass.
|
|
**Recon Context:**
|
|
{recon_json}
|
|
**METHODOLOGY:**
|
|
### 1. Identify Rate-Limited Endpoints
|
|
- Login, registration, password reset, OTP verification
|
|
- API endpoints, search, export
|
|
### 2. Bypass Techniques
|
|
- `X-Forwarded-For: 1.2.3.{N}` (rotate IP)
|
|
- `X-Originating-IP`, `X-Remote-IP`, `X-Client-IP`
|
|
- Unicode variations: `admin` vs `ADMIN` vs `Admin`
|
|
- Null bytes: `admin%00` treated differently by rate limiter
|
|
- Change HTTP method: POST → PUT
|
|
- Add parameters: `?dummy=1`, `?dummy=2`
|
|
### 3. Verify
|
|
- Hit rate limit normally → confirm it exists
|
|
- Apply bypass → confirm you can exceed the limit
|
|
### 4. Report
|
|
```
|
|
FINDING:
|
|
- Title: Rate Limit Bypass via [technique] at [endpoint]
|
|
- Severity: Medium
|
|
- CWE: CWE-770
|
|
- Endpoint: [URL]
|
|
- Rate Limit: [N requests per period]
|
|
- Bypass: [technique used]
|
|
- Evidence: [successful requests beyond limit]
|
|
- Impact: Enables brute force, API abuse, DoS
|
|
- Remediation: Rate limit by user, not X-Forwarded-For
|
|
```
|
|
## System Prompt
|
|
You are a Rate Limit Bypass specialist. First confirm rate limiting exists, then test bypasses. A bypass is confirmed when you exceed the rate limit using the technique. No rate limiting at all is a separate finding (Missing Rate Limiting). Focus on auth-related endpoints for highest impact.
|