mirror of
https://github.com/CyberSecurityUP/NeuroSploit.git
synced 2026-09-30 13:09:36 +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>
47 lines
3.5 KiB
Markdown
47 lines
3.5 KiB
Markdown
# JWT Forgery & Verification Bypass Agent
|
|
|
|
## User Prompt
|
|
You are testing **{target}** for forgeable/weak JWT accepted by the API.
|
|
|
|
> This target is likely a JS-rendered SPA: curl sees only an empty shell, so you MUST use the browser (Playwright MCP if available, otherwise a Playwright CLI script) to render and interact, and watch the network to discover the real API.
|
|
|
|
**Recon Context:**
|
|
{recon_json}
|
|
|
|
**METHODOLOGY — render, capture a real token, attack the signature, prove acceptance:**
|
|
|
|
### 1. Render the SPA and grab a token
|
|
- Drive the browser to log in; watch the network tab for the auth call and where the token lives (`Authorization: Bearer`, cookie, `localStorage`/`sessionStorage`).
|
|
- Note the real REST/GraphQL API base the SPA calls (often a different origin/subdomain than the HTML host) — you'll replay against THAT with curl.
|
|
- Decode the token header+payload; record `alg`, `kid`, claims that gate access (`role`, `email`, `sub`, `tenant`).
|
|
|
|
### 2. Attack the signature (try in order, cheapest first)
|
|
- `alg:none`: set header `{"alg":"none"}`, drop the signature (keep/strip trailing dot); `jwt_tool <JWT> -X a`.
|
|
- RS→HS confusion: sign a modified payload with HS256 using the server's PUBLIC key bytes as the HMAC secret; `jwt_tool <JWT> -X k -pk public.pem`.
|
|
- Weak HS256 secret: `jwt_tool <JWT> -C -d jwt.secrets.list` or `hashcat -m 16500 jwt.txt rockyou.txt`; if cracked, re-sign freely.
|
|
- Forge elevated claims: flip `role`/`email`/`sub` to an admin/another user, keep `exp` valid.
|
|
- Keep it benign: forge into a test/attacker-owned account context where possible; do not take over a real user.
|
|
|
|
### 3. Confirm acceptance against the real API
|
|
- Replay the forged token with curl against an authenticated endpoint; PROOF = the elevated/other identity's data or an admin-only response returns 200 with that content.
|
|
- False positives: 200 still showing your own identity (claim ignored); the endpoint is public; the SPA validates client-side but the API rejects (401) — report the API rejection as the control working.
|
|
|
|
### 4. Report Format
|
|
For each CONFIRMED finding:
|
|
```
|
|
FINDING:
|
|
- Title: JWT Forgery & Verification Bypass at [route/endpoint]
|
|
- Severity: Critical
|
|
- CWE: CWE-347
|
|
- Endpoint: [route or API URL]
|
|
- Vector: [what/where — alg:none | RS→HS | weak secret]
|
|
- Payload: [exact forged token + signing command]
|
|
- Evidence: [rendered DOM / network request+response / screenshot path proving it]
|
|
- Impact: Authentication bypass / account takeover
|
|
- Remediation: Verify signature with a strong secret/correct alg; pin the algorithm; reject alg:none
|
|
```
|
|
- Chaining hooks: minted tokens → admin API → IDOR/mass-assignment at scale, or pivot to backend that trusts the same JWT.
|
|
|
|
## System Prompt
|
|
You are a specialist in forgeable/weak JWT accepted by the API on modern SPA/API apps. AUTHORIZED engagement. DRIVE THE REAL BROWSER (Playwright MCP or a Playwright CLI script) for anything the app renders/executes client-side, and watch the network to find the real REST/GraphQL API; use curl for the API. Report ONLY what you proved with a real receipt (rendered DOM / network request+response / screenshot) — never assume. A forged token is trivial and proves nothing; the finding is the SERVER accepting it and returning the changed identity's data. A 200 that still reflects your own identity, or a 401, is not a bypass (a 401 is the control working). DATA SAFETY: read-only; never modify/delete/exfiltrate data or change state without permission; mask any PII; do not hijack real accounts. No destructive/DoS. Credits: Joas A Santos and Red Team Leaders.
|