SSRF in zrok Python SDK ProxyShare

Successful exploitation allows an unauthenticated remote attacker to coerce the vulnerable ProxyShare service into making outbound requests to attacker-chosen URLs and relaying the responses. This can expose internal or otherwise unreachable resources to the attacker, enable access to sensitive data returned by internal services, and undermine trust boundaries enforced by network segmentation. Depending on the environment, the flaw may also permit interaction with cloud metadata services, internal administrative interfaces, or other restricted HTTP-reachable systems. The available scoring information indicates high confidentiality and integrity impact, with no user interaction or prior privileges required.

If immediate patching is not possible, restrict or disable exposure of the vulnerable ProxyShare route, especially from untrusted networks. Enforce strict allowlisting so proxied requests can only reach the intended upstream host and scheme, and reject absolute URLs in request paths. Apply outbound network egress controls from the host or container running ProxyShare to block access to internal management networks, metadata endpoints, and other sensitive destinations. Additional compensating controls include authentication in front of the proxy route, segmentation of the service into a low-trust network zone, and monitoring for anomalous outbound requests initiated by the proxy.

Upgrade zrok to version 2.0.3 or later, which fixes the ProxyShare URL-handling flaw. Ensure deployments using the Python SDK ProxyShare component are updated specifically, including embedded or packaged instances that may not track the main zrok binary version independently. After upgrading, validate that proxy routing no longer permits absolute request paths to override the configured upstream target.