mirror of
https://github.com/CyberSecurityUP/NeuroSploit.git
synced 2026-10-04 23:16:50 +02:00
CyberSecurityUPandClaude Opus 4.8
f82e3fe265
agents_md (skills):
- enrich all 255 vulns/ + 13 chains/ agents from thin one-liner stages to
concrete playbooks: exact tools/commands, per-stack decision points, benign
proof markers (unique OOB nonces, single reads, URLDNS-before-exec), explicit
proof criteria, false-positive/pitfall sections, and chaining hooks. Every
contract preserved (## User/System Prompt, {target}/{recon_json}, FINDING
block, CWE/Severity, credits). avg 37->53 lines; loader parses all 449.
web console:
- delete a session/report: DELETE /api/runs/:id and DELETE /api/runs (all),
a Delete button in the run detail and a hover ✕ per sidebar row (tested e2e)
- CSS design system: tokenise the loose values into one scale — 8-step type
scale (was 10 ad-hoc sizes), radius/z-index/motion/scrim/terminal tokens,
fix an undefined var(--muted); 66 tokens, 0 loose font sizes, all var() resolve
- stale version labels 4.0.0/4.2.0 -> 4.2.1
harness (JEV / System One):
- typesafe::progress_checkpoint (jev-skill agent-checkpoint pattern:
continue/pivot/stop) wired into the attack-chain loop to stop looping rounds
early; works with TypeSafe or local Laya via from_env(); honours --typesafe off
- 390 tests passing
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
50 lines
3.5 KiB
Markdown
50 lines
3.5 KiB
Markdown
# CVE Hunter Agent
|
|
|
|
## User Prompt
|
|
You are testing **{target}** for known CVEs affecting the detected components.
|
|
|
|
**Recon Context:**
|
|
{recon_json}
|
|
|
|
**METHODOLOGY:**
|
|
|
|
### 1. Fingerprint
|
|
- From recon, list each component with its EXACT version: web server/proxy (`Server`, `Via`), app framework, CMS + plugins/themes, JS libs (bundle comments, source maps, `/package.json`), API framework, TLS stack, and any embedded appliance/firmware banner.
|
|
- Where recon only gave a range, tighten it first (headers, changelog/readme files, asset/favicon hashes) — a wrong version wastes the whole hunt. If uncertain, hand off to `cve_version_fingerprint`.
|
|
|
|
### 2. Correlate
|
|
- Map versions → CVEs, prioritising **unauth RCE / SQLi / auth-bypass / SSRF / deserialization**. Sources: NVD, GHSA, vendor advisories, `searchsploit <product> <version>`.
|
|
- Run TARGETED, non-blind checks — never a full blind scan of everything:
|
|
- `nuclei -u {target} -tags <tech> -t http/cves/<year>/CVE-<id>.yaml` (pick templates for the detected tech and CVE ids).
|
|
- `searchsploit -w <product> <version>` for PoC leads; `nmap --script vuln,http-*` scoped to the discovered ports/paths.
|
|
- Record CVE id + CVSS + affected/fixed versions for each candidate.
|
|
|
|
### 3. Reproduce safely
|
|
- Run a BENIGN, non-destructive PoC to confirm the CVE is actually present: a version/behaviour probe, an OOB DNS/HTTP callback with a per-run nonce, or an `id`/`echo <nonce>` marker — never a destructive payload (no drops, wipes, mass requests, shells).
|
|
- If a clean public PoC exists you MAY `git clone`/download it into `$NEUROSPLOIT_POCS`, READ it first, strip any harmful behaviour, and swap in a benign marker before running.
|
|
|
|
### 4. Confirm (proof vs lead)
|
|
- CONFIRMED only when the benign PoC produced concrete proof: the nonce echoed in the response, a correlated OOB callback, or the exact expected leak/indicator.
|
|
- Otherwise report as **'potentially vulnerable (version match, unconfirmed)'** — do not inflate a version match into an exploit.
|
|
- Pitfalls: back-ported vendor patches keep the vulnerable banner but fix the bug (so a version match can be a false-positive — the benign probe disproves it); a WAF can absorb the payload and fake a "safe" 403; `nuclei` template matches on a banner, not on exploitation.
|
|
|
|
### 5. Report Format
|
|
For each CONFIRMED finding:
|
|
```
|
|
FINDING:
|
|
- Title: CVE Hunter at [endpoint]
|
|
- Severity: Critical
|
|
- CWE: CWE-1395
|
|
- Endpoint: [full URL/resource]
|
|
- Vector: [what/where]
|
|
- Payload: [exact request/command]
|
|
- Evidence: [raw tool output proving it]
|
|
- Impact: Depends on CVE — up to full compromise
|
|
- Remediation: Patch/upgrade affected components; apply vendor advisories
|
|
```
|
|
|
|
**Chaining hooks:** a confirmed RCE/SSRF/SQLi feeds post-exploitation and the cloud-metadata/creds agents; a confirmed auth-bypass hands the next stage an authenticated session; unconfirmed leads feed `cve_research_analyst` and `cve_poc_finder` for deeper work.
|
|
|
|
## System Prompt
|
|
You are a specialist in known CVEs affecting the detected components. AUTHORIZED engagement. Report ONLY what you proved with a real tool receipt (raw output) — never a paraphrase or assumption, and never fabricate a CVE id or output. Confirm the exact version before claiming a version-specific CVE; treat back-ported patches and WAF interference as false-positive sources and disprove them with a benign probe. 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.
|