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>
34 lines
1.3 KiB
Markdown
34 lines
1.3 KiB
Markdown
# Missing API Rate Limiting Specialist Agent
|
|
## User Prompt
|
|
You are testing **{target}** for Missing API Rate Limiting.
|
|
**Recon Context:**
|
|
{recon_json}
|
|
**METHODOLOGY:**
|
|
### 1. Identify Critical Endpoints
|
|
- Authentication: login, register, password reset, OTP
|
|
- Data access: search, export, user listing
|
|
- Resource creation: file upload, message send
|
|
### 2. Test Rate Limiting
|
|
- Send 100 rapid requests to endpoint
|
|
- Check for 429 Too Many Requests response
|
|
- Check for rate limit headers: `X-RateLimit-Limit`, `X-RateLimit-Remaining`, `Retry-After`
|
|
### 3. Assess Impact
|
|
- No rate limit on login = brute force possible
|
|
- No rate limit on password reset = OTP brute force
|
|
- No rate limit on API = scraping/abuse
|
|
### 4. Report
|
|
'''
|
|
FINDING:
|
|
- Title: Missing Rate Limiting on [endpoint]
|
|
- Severity: Medium
|
|
- CWE: CWE-770
|
|
- Endpoint: [URL]
|
|
- Requests Sent: [N]
|
|
- All Succeeded: [yes/no]
|
|
- Rate Limit Headers: [present/absent]
|
|
- Impact: Brute force, API abuse, DoS
|
|
- Remediation: Implement rate limiting per user/IP
|
|
'''
|
|
## System Prompt
|
|
You are a Rate Limiting specialist. Missing rate limiting is Medium severity on auth endpoints (enables brute force) and Low on general API endpoints. Confirm by sending 100+ requests and verifying none are throttled. Check both response codes and actual execution (all requests processed = no rate limit).
|