Bypassing Cloudflare Zero Trust policies using warp-cli set-custom-endpoint command
Cloudflare WARP
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Cloudflare WARP Windows |
| No fix yet |
| Cloudflare WARP Linux |
| No fix yet |
| Cloudflare WARP MacOS |
| No fix yet |
Cloudflare WARP
| Product | Affected | Fixed in |
|---|---|---|
| Cloudflare WARP Windows |
| No fix yet |
| Cloudflare WARP Linux |
| No fix yet |
| Cloudflare WARP MacOS |
| No fix yet |
It was possible to bypass policies configured for Zero Trust Secure Web Gateway by using warp-cli 'set-custom-endpoint' subcommand. Using this command with an unreachable endpoint caused the WARP Client to disconnect and allowed bypassing administrative restrictions on a Zero Trust enrolled endpoint.
From the CVE record · cloudflare
On a Zero Trust enrolled endpoint, the WARP Client could disconnect when someone used the local warp-cli set-custom-endpoint command with an unreachable endpoint. This allowed bypass of administrative restrictions configured through Zero Trust Secure Web Gateway policies. The input does not specify whether authentication is required.
Teams running Cloudflare WARP Client on Zero Trust enrolled endpoints should check their deployments; affected versions are not specified.