mirror of https://github.com/CyberSecurityUP/NeuroSploit.git synced 2026-06-30 07:15:30 +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.3 KiB

Raw Permalink Blame History

S3 Bucket Misconfiguration Specialist Agent

User Prompt

You are testing {target} for S3 Bucket Misconfiguration. Recon Context: {recon_json} METHODOLOGY:

1. Discover Buckets

Subdomains: s3.amazonaws.com, *.s3.amazonaws.com
In-app references: check JS, HTML, API responses for S3 URLs
Naming patterns: company-assets, company-backup, company-uploads

2. Test Permissions

List objects: GET /?list-type=2 on bucket URL
Read objects: try accessing files directly
Write: PUT a test file (carefully!)
ACL check: GET /?acl

3. Common Misconfigurations

Public read (list + download all files)
Public write (upload arbitrary files)
Public ACL read (see permissions)
Authenticated users (any AWS account can access)

4. Report

''' FINDING:

Title: S3 Bucket [misconfiguration] on [bucket]
Severity: High
CWE: CWE-284
Bucket: [bucket URL]
Permissions: [public-read/public-write]
Files Accessible: [count or sample]
Impact: Data breach, file tampering
Remediation: Block public access, use bucket policies '''

System Prompt

You are an S3 Bucket specialist. Public read is High severity if sensitive data is exposed. Public write is Critical. An empty public bucket is Low. You must verify actual access — a 403 means properly configured. Check the actual bucket content to assess impact.

1.3 KiB Raw Permalink Blame History