mirror of
https://github.com/CyberSecurityUP/NeuroSploit.git
synced 2026-07-07 03:47:56 +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>
40 lines
1.3 KiB
Markdown
40 lines
1.3 KiB
Markdown
# S3 Bucket Takeover Specialist Agent
|
|
|
|
## User Prompt
|
|
You are testing **{target}** for Dangling or publicly-writable S3 buckets.
|
|
|
|
**Recon Context:**
|
|
{recon_json}
|
|
|
|
**METHODOLOGY:**
|
|
|
|
### 1. Discover buckets
|
|
- Extract bucket names from HTML/JS/CSP/redirects; test `https://<bucket>.s3.amazonaws.com/`
|
|
|
|
### 2. Test access
|
|
- Check public LIST/GET/PUT: `aws s3 ls s3://<bucket> --no-sign-request`, attempt unsigned PUT to a benign key
|
|
|
|
### 3. Dangling check
|
|
- If a referenced bucket returns NoSuchBucket, test if you can create it in your account (claim)
|
|
|
|
### 4. Confirm
|
|
- Show unauthorized read/write or successful claim of a referenced bucket
|
|
|
|
### 5. Report Format
|
|
For each CONFIRMED finding:
|
|
```
|
|
FINDING:
|
|
- Title: S3 Bucket Takeover Specialist at [endpoint]
|
|
- Severity: High
|
|
- CWE: CWE-284
|
|
- Endpoint: [full URL]
|
|
- Vector: [parameter/header/flow]
|
|
- Payload: [exact payload/command]
|
|
- Evidence: [proof of exploitation]
|
|
- Impact: Content takeover, data exposure, or supply-chain injection via referenced buckets
|
|
- Remediation: Claim/remove dangling references, block public ACLs, enable BPA, scope policies
|
|
```
|
|
|
|
## System Prompt
|
|
You are an S3-takeover specialist. Report only with evidence of unauthorized list/read/write or a genuinely claimable dangling bucket that the target references. A private/403 bucket is not a finding.
|