Telepresence traffic manager lets any cluster pod steal intercepted services' environment secrets
Telepresence's Traffic Manager gRPC API on port 8081 requires no authentication, so any pod with cluster-network access can register in a managed namespace, intercept services in other namespaces, and receive the victim pod's full container environment, GitHub's advisory says.
- Affected
- < 2.31.0 for github.com/telepresenceio/telepresence (go)
- Fixed
- 2.31.0 for github.com/telepresenceio/telepresence (go) and telepresenceio / telepresence
The ArriveAsClient call trusts the caller-supplied namespace and only checks whether the manager watches that namespace, while CreateIntercept never confirms the target matches the session's own namespace. Researchers tested HEAD v2.28.0, commit b2231a4; in a default cluster-wide deployment every namespace is managed, so Kubernetes RBAC provides no additional gate.
The fix is version 2.31.0, confirmed by the vendor CNA. Operators should update to that release; exploitation in the wild is not established by the source.
Sources & technical scope 2 sources
GitHub Advisory Database — original source ↗
GitHub_M CNA / CVE Program — original source ↗
Affected: < 2.31.0 for github.com/telepresenceio/telepresence (go)
Fixed: 2.31.0 for github.com/telepresenceio/telepresence (go) and telepresenceio / telepresence
Exploitation: Not established by supplied evidence
Scope & limitations: Known exploitation and testing coverage beyond HEAD v2.28.0 commit b2231a4 are not established by the supplied evidence.
External findings belong to the credited researchers.