dbcve.org
WarpApplication · Cloudflare

CVE-2022-3320

CRITICAL · 9.8 CVSS v3.1 Published 2022-10-28
Fix available
A fix is available. Upgrade to 2022.8.857.0 / 2022.8.861.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The WARP client contains a vulnerability where the 'set-custom-endpoint' subcommand, when used with an unreachable endpoint, causes the client to disconnect from the Zero Trust secure web gateway. This disconnection allows bypass of administrative policies and restrictions enforced on Zero Trust enrolled endpoints.

MitigationApply the vendor patch or update the WARP client to a version that addresses this vulnerability. Until then, monitor for unauthorized use of the set-custom-endpoint command and consider additional controls on endpoint configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WarpApplication
Affected:< 2022.8.857.0< 2022.8.861.0< 2022.8.936

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WARP client is installed
    Check for the Cloudflare WARP client on the system. On Windows: look in Program Files or registry. On macOS: check /Applications for Cloudflare WARP.app. On Linux: query package manager (dpkg -l | grep warp, rpm -qa | grep warp) or check /opt/cloudflare-warp.
    Affected if WARP client is found on the system
  2. Identify installed WARP version
    Run the WARP client version check. On Windows/macOS: right-click the WARP icon in system tray and select About or check within the app settings. On Linux: run warp-cli version or warp-cli settings to see version info. Alternatively, check the installed package version via system package manager.
    Affected if Installed version is earlier than 2022.8.857.0, 2022.8.861.0, or 2022.8.936 (depending on platform/release channel)
  3. Check for set-custom-endpoint usage
    Review command history (bash history, PowerShell history, Windows Event Logs for process execution) for occurrences of 'warp-cli set-custom-endpoint' or the set-custom-endpoint subcommand being invoked.
    Affected if The set-custom-endpoint command has been executed on the system
  4. Review WARP connection status and policy enforcement gaps
    Check WARP client connection logs (Windows: %ProgramData%\Cloudflare\logs\ or within the app logs. macOS: /Library/Logs/Cloudflare/. Linux: /var/log/cloudflare-warp/ or via journalctl). Look for disconnections, failed endpoint connections, or unexpected loss of Zero Trust gateway enforcement.
    Affected if The WARP client shows disconnected state or loss of Zero Trust policy enforcement following use of set-custom-endpoint with an unreachable endpoint

A system is affected if Cloudflare WARP is installed with a version earlier than 2022.8.857.0/2022.8.861.0/2022.8.936 and the set-custom-endpoint command has been used to disconnect from the Zero Trust secure web gateway.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2022.8.857.0 / 2022.8.861.0 / 2022.8.936 or later
Fixed in 2022.8.857.02022.8.861.02022.8.936
Interim mitigation

Apply the vendor patch or update the WARP client to a version that addresses this vulnerability. Until then, monitor for unauthorized use of the set-custom-endpoint command and consider additional controls on endpoint configuration.

Recommended fix Moderate confidence

WARP version 2022.8.936 or later (or minimum 2022.8.857.0/2022.8.861.0 which contain the fixes)

  1. 1. Identify the current version of Cloudflare WARP client installed on affected systems using 'warp-cli --version' or checking the application UI
  2. 2. For Windows/macOS: Download the latest WARP client from the official Cloudflare download page
  3. 3. For Linux: Update via package manager (e.g., 'sudo apt-get update && sudo apt-get install warp-svc' for Debian/Ubuntu, or 'sudo yum update warp-svc' for RHEL/CentOS)
  4. 4. Verify the installed version is 2022.8.936 or later using 'warp-cli --version'
  5. 5. Test that the 'set-custom-endpoint' command no longer bypasses administrative restrictions when used with unreachable endpoints
  6. 6. Verify Zero Trust Secure Web Gateway policies are properly enforced after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Warp Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3320 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-3320 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data