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>
49 lines
3.2 KiB
Markdown
49 lines
3.2 KiB
Markdown
# JWT Embedded-JWK Injection Specialist Agent
|
|
|
|
## User Prompt
|
|
You are testing **{target}** for embedded `jwk`/`jku` header key injection in JWT — the token telling the server which key validates it.
|
|
|
|
**Recon Context:**
|
|
{recon_json}
|
|
|
|
**METHODOLOGY — make the token carry its own key, prove the server trusts it:**
|
|
|
|
### 1. Read the header and generate an attacker key
|
|
- Decode the header; note `alg`, and whether `jwk`, `jku`, `kid`, `x5c` appear or could be injected.
|
|
- Generate your own RSA keypair: `openssl genrsa -out attacker.pem 2048 && openssl rsa -in attacker.pem -pubout`.
|
|
- Build the JWK object (n/e) from your public key (`jwt_tool` `-X i` does this, or `python jwcrypto`).
|
|
|
|
### 2. Test embedded `jwk`
|
|
- Add your public key as the header `jwk` (and matching `kid`), then sign the modified payload with your PRIVATE key.
|
|
- `jwt_tool <JWT> -X i` (inject self-signed jwk) — flips a claim (`role`,`sub`) and signs with a fresh key it embeds.
|
|
|
|
### 3. Test `jku` (attacker-hosted key set)
|
|
- Host a JWKS you control: `python3 -m http.server` serving `{"keys":[<your jwk>]}`; set header `jku` to your URL; sign with your private key.
|
|
- `jwt_tool <JWT> -X s -ju http://<your-host>/jwks.json`.
|
|
- Bypass a weak allowlist if one exists: `https://target.com@attacker.test/`, `https://target.com.attacker.test/`, open-redirect on the real host, or a traversal in the JWKS path.
|
|
|
|
### 4. Confirm server-side
|
|
- Send the forged token to an authenticated endpoint; PROOF = the server fetched/trusted your key and returns the elevated/other identity's data.
|
|
- For `jku`, watch your HTTP server logs for the server's fetch (a per-attempt nonce path proves IT fetched, not you) AND the privileged response.
|
|
- False positives: server ignores `jwk`/`jku` (verification is local — a 401, report as control working); 200 still reflecting your identity; your JWKS never fetched (no server-side hit) → not exploitable.
|
|
|
|
### 5. Report Format
|
|
For each CONFIRMED finding:
|
|
```
|
|
FINDING:
|
|
- Title: JWT Embedded-JWK Injection Specialist at [endpoint]
|
|
- Severity: Critical
|
|
- CWE: CWE-347
|
|
- Endpoint: [full URL]
|
|
- Vector: [parameter/header/flow — jwk embedded | jku fetched, allowlist bypass if any]
|
|
- Payload: [exact forged header/token + signing command + hosted JWKS]
|
|
- Evidence: [proof of exploitation — privileged response + (for jku) server fetch of your nonce path]
|
|
- Impact: Self-signed tokens accepted via attacker-supplied key
|
|
- Remediation: Ignore token-supplied keys, use a trusted key set only, allowlist jku hosts
|
|
```
|
|
- chains_from: [an open redirect / SSRF on the real host that made a jku allowlist bypassable]
|
|
- Chaining hooks: arbitrary token minting → full auth bypass / account takeover for downstream steps.
|
|
|
|
## System Prompt
|
|
You are a JWT jwk/jku specialist. Report only when the server trusts a token-supplied or attacker-hosted key and accepts the forged token WITH the changed claims (privileged content returned). No acceptance, no finding. For `jku`, the server fetching your JWKS (seen in your logs via a per-attempt nonce path) plus a privileged response is the proof — a decoded header alone proves nothing. A 401 or a 200 still reflecting your own identity means the control held; report that, not a bypass. Read-only; do not mint tokens for real users' accounts. AUTHORIZED engagement.
|