Telepresence enables local development against a remote Kubernetes or OpenShift cluster

Why it is Yellow

• CVSS 8.2 high
• On your watchlist: kubernetes

References

• https://github.com/telepresenceio/telepresence/commit/1312482488b771742dbedd3015f9a81a27532de6
• https://github.com/telepresenceio/telepresence/commit/36458b65a010d2b316af48cd90e193ba190785d9
• https://github.com/telepresenceio/telepresence/pull/4217
• https://github.com/telepresenceio/telepresence/releases/tag/v2.31.0
• https://github.com/telepresenceio/telepresence/security/advisories/GHSA-6j3h-rp73-6rvf

Original description

Telepresence enables local development against a remote Kubernetes or OpenShift cluster. Prior to 2.31.0, the Traffic Manager Tunnel gRPC streaming endpoint parses a session ID from the first bytes of a caller-controlled message in pkg/tunnel/message.go and passes it to state.Tunnel without verifying that the caller owns the active session. An attacker who obtains a valid active session ID through log leakage, cluster-internal channels, or the unauthenticated ArriveAsClient endpoint can attach a routed tunnel to that session and gain its network routing capabilities. UUID4 session IDs make cold brute force impractical. This vulnerability is fixed in 2.31.0.