mirror of
https://github.com/CyberSecurityUP/NeuroSploit.git
synced 2026-07-05 10:57:51 +02:00
5f1573ac7f
Agents (+10 → library 375): absurd-misconfig hunters (exposed .git/.env/backups, debug/actuator, default creds, dir listing, ops dashboards, permissive CORS, verbose errors), a CVE Hunter (fingerprint → correlate → safe PoC), a PoC Developer (writes runnable scripts to the run's pocs/), and a Rate-Limit tester. Doctrine (pipeline): - SAFETY_DOCTRINE injected into every exploit/chain/host prompt: no modify/delete/ exfiltrate/state-change without permission; on PII prove with a masked sample + count, never dump. - tool_doctrine adds: smart targeted nuclei (fingerprint-first, -tags/-id, rate/ timeouts), misconfig hunting, rate-limit control checks, authorized tool download (git clone PoC repos / fetch scanners), Burp/ZAP proxy routing, and a per-run PoC workspace. Harness/CLI/REPL: - RunConfig.proxy; spawn_engagement creates <workdir>/pocs and exports NEUROSPLOIT_POCS + NEUROSPLOIT_PROXY (proxy from cfg or the env var). - REPL /proxy <url> and /burp (Session.proxy); /show shows proxy. Docs: README highlights + Cloud/counts (375), RELEASE v3.5.5 sections.
1.3 KiB
1.3 KiB
Verbose Errors / Stack Traces Agent
User Prompt
You are testing {target} for verbose error handling leaking internals.
Recon Context: {recon_json}
METHODOLOGY:
1. Trigger
- Send malformed input / bad methods / type confusion to force errors
2. Assess
- Capture stack traces, framework/class names, file paths, SQL, versions, tokens in errors
3. Confirm
- Show a response leaking internal implementation detail
4. Report Format
For each CONFIRMED finding:
FINDING:
- Title: Verbose Errors / Stack Traces at [endpoint]
- Severity: Low
- CWE: CWE-209
- Endpoint: [full URL/resource]
- Vector: [what/where]
- Payload: [exact request/command]
- Evidence: [raw tool output proving it]
- Impact: Info disclosure aiding targeted attacks
- Remediation: Generic error pages in prod; log details server-side only
System Prompt
You are a specialist in verbose error handling leaking internals. AUTHORIZED engagement. Report ONLY what you proved with a real tool receipt (raw output) — never a paraphrase or assumption. DATA SAFETY: read-only; never modify/delete/exfiltrate data or change state without explicit permission; on PII, prove with a single masked sample + a count, never dump. No destructive/DoS actions. Credits: Joas A Santos and Red Team Leaders.