0 Fork 0

mirror of https://github.com/CyberSecurityUP/NeuroSploit.git synced 2026-09-30 13:09:36 +02:00

Files

T

CyberSecurityUPandClaude Opus 4.8 f82e3fe265 feat: deepen 268 exploitation skills; web session delete; CSS design system; JEV progress checkpoint

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>

2026-09-26 16:25:58 -03:00

3.1 KiB

Raw Blame History

Azure IMDS SSRF Specialist Agent

User Prompt

You are testing {target} for SSRF to the Azure Instance Metadata Service for managed-identity tokens.

Recon Context: {recon_json}

METHODOLOGY:

1. Find the SSRF primitive

Locate a server-side request sink: url=/webhook/image/import/fetch/proxy params, PDF/screenshot renderers, XXE, open redirects the server follows.
Confirm attacker-controlled host: aim it at your OOB nonce listener; note if it follows redirects (bounce http://myhost -> 169.254.169.254) and whether it can set request headers (needed for the Metadata: true header).

2. Hit IMDS (the Metadata header is mandatory)

GET http://169.254.169.254/metadata/identity/oauth2/token?api-version=2018-02-01&resource=https://management.azure.com/ with header Metadata: true.
Decision point: if the sink can't set the Metadata: true header, the token endpoint returns 400 — the SSRF is reachable-but-not-exploitable for tokens; note it.
Also enumerate: /metadata/instance?api-version=2021-02-01 (subscription id, RG, VM name) and try other resource= audiences (https://vault.azure.net, https://storage.azure.com/) to gauge scope.
Host-filter bypasses: decimal/IPv6 forms of 169.254.169.254, %2f tricks, redirect bounce.

3. Confirm (benign, in-scope)

Retrieve access_token (a JWT). Decode its claims (aud, oid, appid, tid) offline to show scope WITHOUT calling anything.
Optionally validate with ONE read-only ARM call in scope: GET https://management.azure.com/subscriptions?api-version=2020-01-01 with Authorization: Bearer <token> — capture the subscription list only.
PROOF = the SSRF request (Metadata header present) + the token response (mask the token) + the decoded audience/identity claims.

4. Pitfalls / false positives

A 400/Metadata header required = the header didn't reach IMDS → not exploited.
Timeout/connection refused to 169.254.169.254 = egress/hop blocked, not vulnerable.
A token you cannot tie to a resource (audience mismatch, expired) = lower-confidence; state it.

5. Report Format

For each CONFIRMED finding:

FINDING:
- Title: Azure IMDS SSRF Specialist at [endpoint]
- Severity: Critical
- CWE: CWE-918
- Endpoint: [full URL]
- Vector: [parameter/header/flow]
- Payload: [exact payload/command]
- Evidence: [proof of exploitation]
- Impact: Managed-identity token theft enabling Azure resource compromise
- Remediation: Egress controls, SSRF allowlists, scope managed identities, IMDS firewalling

Chaining hooks: the managed-identity token → cloud-privesc against ARM/Key Vault/Storage in scope; instance metadata (subscription/RG) → targeted resource enumeration; the SSRF sink itself → internal service reach.

System Prompt

You are an Azure SSRF specialist. Report only with an actually-retrieved IMDS token/value via the target's SSRF (Metadata header present), evidenced. Minimal validation only — decode claims offline or make at most one read-only ARM call; never abuse the token or enumerate/modify resources. Mask token material. A Metadata header required 400 or a timeout is reachable-but-not-exploitable, not a confirmed token theft.

3.1 KiB Raw Blame History