WarpApplication · Cloudflare

CVE-2020-35152

HIGH · 7.8 CVSS v3.1 Published 2021-02-03
Fix available
A fix is available. Upgrade to 1.2.2695.1 or later.
See remediation →
80/100
Remediation priority · High
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
Cloudflare WARP for Windows allows privilege escalation due to an unquoted service path. A malicious user or process running with non-administrative privileges can become an administrator by abusing the unquoted service path issue. Since version 1.2.2695.1, the vulnerability was fixed by adding quotes around the service's binary path. This issue affects Cloudflare WARP for Windows, versions prior to 1.2.2695.1.

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 · high confidence

Cloudflare WARP for Windows contains an unquoted service path vulnerability where the service binary path contains spaces and is not enclosed in quotation marks. This allows a local attacker to place a malicious executable in an intermediate path directory and achieve arbitrary code execution with elevated (SYSTEM) privileges, enabling privilege escalation from non-administrative to administrator access.

MitigationUpgrade Cloudflare WARP for Windows to version 1.2.2695.1 or later, which fixes the vulnerability by properly quoting the service binary path in the Windows service 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:< 1.2.2695.1

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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. Check if Cloudflare WARP service is installed
    Run 'sc query warp' or 'Get-Service -Name warp' in PowerShell/Command Prompt
    Affected if The service does not exist, meaning WARP is not installed and the system is not affected.
  2. Retrieve the service binary path configuration
    Run 'sc qc warp' (Command Prompt) or '(Get-WmiObject Win32_Service -Filter "Name='warp'").PathName' (PowerShell)
    Affected if A path is returned that contains spaces and is NOT enclosed in quotation marks (e.g., C:\Program Files\Cloudflare\WARP\warp.exe instead of "C:\Program Files\Cloudflare\WARP\warp.exe").
  3. Verify the installed version of Cloudflare WARP
    Run '"C:\Program Files\Cloudflare\WARP\warp.exe" --version' or check the registry at 'HKLM\SOFTWARE\Cloudflare\WARP' for the Version value
    Affected if The installed version is lower than 1.2.2695.1.
  4. Inspect intermediate directories in the service path
    Examine each folder in the unquoted path (e.g., if path is C:\Program Files\Cloudflare\WARP\warp.exe, check C:\Program Files\ and C:\Program Files\Cloudflare\) for any unexpected or malicious executables
    Affected if A malicious executable with a matching intermediate path component name (e.g., Program.exe in C:\) is found, indicating potential exploitation.

A user is affected if the Cloudflare WARP service is installed, the service binary path contains spaces without quotation marks, and the installed version is below 1.2.2695.1.

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.

From vendor data
Upgrade available Upgrade to 1.2.2695.1 or later
Fixed in 1.2.2695.1
Interim mitigation

Upgrade Cloudflare WARP for Windows to version 1.2.2695.1 or later, which fixes the vulnerability by properly quoting the service binary path in the Windows service configuration.

Fix this in Warp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2020-35152 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