Telepresence enables local development against a remote Kubernetes or OpenShift cluster

Why it is Amber

• CVSS 8.5 high
• On your watchlist: kubernetes

References

• https://github.com/telepresenceio/telepresence/commit/04ec3464fe8878fdc96420cdc8036edefa0dc9ae
• https://github.com/telepresenceio/telepresence/commit/36458b65a010d2b316af48cd90e193ba190785d9
• https://github.com/telepresenceio/telepresence/commit/6871235b674a6e843908d09696354c4b0f91578c
• 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-j8j4-rw65-56r6

Original description

Telepresence enables local development against a remote Kubernetes or OpenShift cluster. Prior to 2.31.0, the Traffic Manager gRPC API on port 8081 accepts unauthenticated cluster-network callers, ArriveAsClient stores a caller-supplied Namespace using only the ManagesNamespace manager watchlist check, and CreateIntercept can target any managed namespace without checking the session's Kubernetes RBAC. An attacker operating any pod with network access to the manager can register in an arbitrary managed namespace, create service intercepts, receive intercepted traffic, and obtain the victim pod's complete container environment, including secrets, tokens, and API keys. The default cluster-wide deployment manages all namespaces. This vulnerability is fixed in 2.31.0.