tilt-dev vulnerabilities and threats

Tilt versions from 0.24.0 up to 0.37.3 have a vulnerability in the Tilt HUD WebSocket at /ws/view. The WebSocket is protected by a CSRF token served by an unauthenticated endpoint, and the upgrader accepts clients without an Origin header. This allows an attacker with network access to the HUD WebSocket to receive sensitive information including session state, Tiltfile contents, and resource statuses. The issue is fixed in version 0.37.4.

Tilt defines dev environments as code for microservice apps on Kubernetes. From 0.19.5 through 0.37.3, the Tilt HUD server mounts Go net/http/pprof handlers under /debug with no access control. When the HUD or apiserver listener is network-exposed, an unauthenticated caller can read process memory through /debug/pprof/heap and /debug/pprof/goroutine, including session and apiserver tokens, and degrade performance through /debug/pprof/profile or /debug/pprof/trace. This issue is fixed in version 0.37.4.

Tilt defines dev environments as code for microservice apps on Kubernetes. From 0.20.8 through 0.37.3, the Tilt HUD HTTP server registers handlers on a gorilla/mux router with no authenticating middleware. When the HUD is bound to a non-loopback address, an unauthenticated network caller can trigger developer-defined resources, tamper with Tiltfile arguments, read full engine state including the session token, and invoke apiserver resources through the token-attaching /proxy handler. This issue is fixed in version 0.37.4.