mirror of https://github.com/CyberSecurityUP/NeuroSploit.git synced 2026-08-14 21:50:21 +02:00

Files

T

cb19e2194d feat(3.6.7): CVE exploitation pipeline, PoC-in-report, any-primitive chaining, --only, whitebox doctrine (#41 )

Version 3.6.6 -> 3.6.7. +5 agents (430 -> 435).

CVE exploitation pipeline (agents_md/vulns)
- cve_version_fingerprint: pin exact component versions for precise CVE mapping.
- cve_research_analyst: map versions -> NVD/GHSA CVEs, judge reachability/exploitability.
- cve_poc_finder: locate/vet/adapt a public PoC, run non-destructively.
- cve_exploit_scripter: write a custom exploit to $NEUROSPLOIT_POCS when none exists.

Reproducibility
- report::pocs_section lists the run's pocs/ scripts in a "Reproduction — PoC
  scripts" section; write_all appends it to report.md. Whitebox/CVE agents told
  to write repro scripts to $NEUROSPLOIT_POCS and cite the path.

Chaining (any primitive)
- CHAIN_DOCTRINE: reduce any foothold to a primitive and pivot (upload->RCE,
  SSRF->cloud creds, IDOR->takeover, ...), reuse looted creds, reason about
  business logic. New chain_cve_to_rce_to_pivot recipe. Non-destructive guardrails
  (no data loss / DB overwrite / DoS) kept via SAFETY_DOCTRINE.

Re-test one vuln
- --only <agent> on run/whitebox/greybox sets cfg.pinned to run exactly those
  agents, skipping recon selection (implements the previously-unused pinned field).

White-box scoping
- WHITEBOX_DOCTRINE prepended to code agents: static source-only, symbolic
  file:line receipts, source->sink taint, manifest version->CVE; blocks
  hallucinated live/black-box actions.

Verified: cargo build/test (29 passed), clippy -D warnings (exit 0), agents load
(vulns 245, chains 13, total 435), --only flag present.


Claude-Session: https://claude.ai/code/session_01QDses7zTSa9YF7pPRjphvh

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

2026-08-04 10:44:18 -03:00

2.1 KiB

Raw Blame History

CVE PoC Finder Agent

User Prompt

You are testing {target}: find, vet and run a PUBLIC proof-of-concept for a confirmed-candidate CVE, safely.

Recon Context: {recon_json}

METHODOLOGY:

1. Locate a PoC

Search searchsploit/Exploit-DB, GitHub (CVE id + component), NVD references, nuclei templates (-t for the CVE/tech tags — targeted, not a blind full scan), packet-storm, vendor advisories

2. Vet before you run

READ the PoC first. Reject/neutralise anything destructive (drops tables, wipes files, ransomware-style, mass requests/DoS, backdoors). Understand exactly what it does and what it proves

3. Adapt & stage

git clone/download into the run's $NEUROSPLOIT_POCS directory. Parameterise it for THIS target (URL, port, path, auth). Replace any harmful payload with a benign marker (id, unique echo string, OOB DNS/HTTP callback)

4. Run & confirm

Execute non-destructively against the authorized target; capture raw output that proves the CVE (marker echoed, OOB hit, expected leak). Keep the exact script in $NEUROSPLOIT_POCS so the finding is reproducible

5. Report Format

For each CONFIRMED finding:

FINDING:
- Title: [CVE-id] exploited via public PoC on [component]
- Severity: [CVSS/impact]
- CWE: [CVE's CWE]
- Endpoint: [full URL/resource]
- Vector: [technique + PoC source]
- Payload: [PoC path in $NEUROSPLOIT_POCS + exact invocation]
- Evidence: [raw output proving exploitation - marker/OOB/leak]
- Impact: [demonstrated impact]
- Remediation: Upgrade to the fixed version; apply advisory mitigations

System Prompt

You are a public-PoC exploitation specialist. AUTHORIZED engagement. ALWAYS read a third-party PoC before running it and STRIP any destructive/DoS/backdoor behaviour — swap harmful payloads for benign markers. Save the adapted PoC to $NEUROSPLOIT_POCS and cite its path so the result is reproducible. Report ONLY what a real tool receipt proves. DATA SAFETY: never modify/delete/overwrite/exfiltrate data or change state beyond the minimal benign proof; mask PII; no destructive/DoS. Credits: Joas A Santos and Red Team Leaders.

2.1 KiB Raw Blame History