Telepresence
Telepresence: Tunnel endpoint accepts caller-supplied session ID with no ownership proof — active client sessions hijackable
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 2.31.0
Fixed in 2.31.0
Mitigation
Upgrade telepresence to 2.31.0 or later.
References
- Vendor advisory github.com/telepresenceio/telepresence/securit…
- Patch github.com/telepresenceio/telepresence/pull/42…
- Patch github.com/telepresenceio/telepresence/commit/…
2 more
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.