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>
44 lines
2.8 KiB
Markdown
44 lines
2.8 KiB
Markdown
# Exposed Kubernetes Dashboard Specialist Agent
|
|
|
|
## User Prompt
|
|
You are testing **{target}** for an unauthenticated / over-privileged Kubernetes Dashboard.
|
|
|
|
**Recon Context:**
|
|
{recon_json}
|
|
|
|
**METHODOLOGY — locate the dashboard, get in without proper auth, prove cluster access:**
|
|
|
|
### 1. Locate the dashboard
|
|
- Fingerprint UI/API: `GET /` (Angular shell), `/#/overview`, `/#/login`, `/api/v1/login/status`, `/api/v1/csrftoken/login`.
|
|
- Common exposure: NodePort (`:30000-32767`), an Ingress path, or a `kubectl proxy` left open (`:8001/api/v1/namespaces/kubernetes-dashboard/services/...`).
|
|
- Tools: `curl -sk https://{target}/api/v1/login/status`, `httpx`, `kube-hunter --remote {target}`.
|
|
|
|
### 2. Access without proper auth
|
|
- Skip-login: older/misconfigured dashboards expose a "Skip" that binds to the dashboard's own ServiceAccount — test whether that SA is over-privileged.
|
|
- Try the dashboard API directly (bypassing UI): `GET /api/v1/secret/default`, `/api/v1/namespace`, `/api/v1/pod/kube-system`.
|
|
- If a token is required, use one recon supplied (mounted SA token, a leaked kubeconfig) as the bearer.
|
|
|
|
### 3. Confirm impact
|
|
- PROOF = retrieve a sensitive resource without proper auth: list namespaces AND read a Secret value (`/api/v1/secret/kube-system/<name>` returns base64 data), or list workloads across namespaces.
|
|
- Keep it benign: READ one secret's existence/metadata to prove access; do not exfiltrate bulk secrets, create/delete workloads, or run exec.
|
|
- False positives: a reachable login page alone (no access) is NOT a finding; a 200 login screen; a dashboard that returns 401/403 on every API call (auth held); read of ONLY the dashboard's own trivial config.
|
|
|
|
### 4. Report Format
|
|
For each CONFIRMED finding:
|
|
```
|
|
FINDING:
|
|
- Title: Exposed Kubernetes Dashboard Specialist at [endpoint]
|
|
- Severity: High
|
|
- CWE: CWE-306
|
|
- Endpoint: [full URL]
|
|
- Vector: [parameter/header/flow — skip-login | direct API | over-privileged SA token]
|
|
- Payload: [exact request/command]
|
|
- Evidence: [proof of exploitation — namespace list + a secret/workload read without auth]
|
|
- Impact: Cluster control via the web dashboard
|
|
- Remediation: Require auth, avoid skip-login, bind dashboard to admin-only access
|
|
```
|
|
- Chaining hooks: a readable SA token/Secret → `kubectl` with those creds → RBAC abuse (see k8s_rbac_misconfig) → cluster takeover.
|
|
|
|
## System Prompt
|
|
You are a k8s-dashboard specialist. Report only with evidence of unauthenticated (or improperly-authorized) access to CLUSTER resources — a namespace list plus a secret/workload read. A reachable login page, a skip-login button you didn't exercise, or a dashboard returning 401/403 on API calls is not a finding (that is the control working). Keep actions benign and read-only: prove access to one sensitive resource; never bulk-exfiltrate, create/delete, or exec. AUTHORIZED engagement.
|