Tactical LogHuntress CTF 2026 // team archive

Days / Day 27 / Web Exploitation / Socket to Me

DAY 27//LANE: WEB EXPLOITATION//STATUS: CORRECT x2

Socket to Me

Web Exploitation SSTTMM Modes reported CORRECT in this write-up

Socket to Me (Day 27, Web Exploitation)

Challenge prompt: "The chat upgraded to websockets and left its manners at the HTTP door. Ride the upgrade into an event stream that was never meant for you."

Flag: Tokenc42fe3b905cbfe7158d4dc7c8284ba48

Single Solve

Target: https://<host>/ (Koa app "Live Case Wire", role=analyst).

  1. GET /api/clues -> {"framework":"Koa","feature_route":"/dispatch-53decf","current_role":"analyst","stream_reference":13777}.
  2. Direct HTTP GET on /dispatch-53decf returns 426 Upgrade Required (WS endpoint).
  3. Plain WS handshake returns 403 Forbidden; the WS auth check reads a query parameter.
  4. wss://<host>/dispatch-53decf?stream=13777 connects and the server immediately pushes: {"ok":true,"effect":"unauthorized_event_stream","evidence":"proof_8f935291d06a4b28ba62ea309ccabe0e"}

The HTTP route is role-gated; the WebSocket upgrade accepts anyone who supplies the integer stream_reference from /api/clues.

Submit: proof-1 = proof_8f935291d06a4b28ba62ea309ccabe0e.

Time Trial

Same shape as Single; the solver's _tech_socket_to_me (added to _TECHNIQUES in solver_copy.py) reads /api/clues, opens the WS at feature_route?stream=<stream_reference>, extracts proof_<hex32> from the first frame. CORRECT in 11.0s (ranked attempt confirmed by GM).

Mastery (lane sampler, 5 distinct web apps)

Classic Day 27 lane sampler bundling five different web vuln classes under one timer. First variant lost (deadline expired while T2/T4 extractors were missing); retry succeeded with the full battery.

TargetTitleTechniqueProof
T1Tiny Uptimerobots_recon → /snapshots-*/ listingProofproof_a1c8064772204af7b853b408a378ef98
T2Incident Picnicsession_idor_cookiejar (/api/events leaks foreign case_id, /api/tickets/<id> IDOR)Proofproof_01c054b596ac48359fd0a4fe3917370f
T3Query Me Thissearch_sqli (GET /explore?q=') OR 1=1--)Proofproof_a1b6c5af96e8431696d2b40922139fa1
T4Runbook Nooklfi_viewer (/notes.php?..., PHP viewer + traversal)Proofproof_34fd71b9b2ec4b5c8694a5b91ced34e8
T5Subscription Desk · Koasocket_to_me (WSS ?stream=<ref> → unauthorized_event_stream)Proofproof_86fc6f0b01e74038b86ad75696def204

Lessons / changes to the battery

  • New technique: _tech_socket_to_me. Reads /api/clues, opens WSS to feature_route?stream=<stream_reference> with matching Origin header, scans first frame for proof_HEX.
  • New technique: _tech_session_idor_cookiejar. The baseline _tech_session_idor goes through web_scope.registered_get, which does not persist cookies across requests, so an implicit session cookie set on / is lost before the /api/events call. The bespoke technique uses a plain urllib HTTPCookieProcessor opener so the case_session cookie flows into every subsequent GET. It also tries /api/tickets, /api/cases, /api/records, /tickets, /cases for the detail route.
  • The all-or-HELD gate in _lfi_handler zeros a partial batch on a ranked timed mode; a missing extractor for one of five targets costs the whole variant. Build every target class into the battery BEFORE autosolve opens the window.