CVE-2022-2147
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 · uneditedCloudflare Warp for Windows from version 2022.2.95.0 contained an unquoted service path which enables arbitrary code execution leading to privilege escalation. The fix was released in version 2022.3.186.0.
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 confidenceCloudflare Warp for Windows version 2022.2.95.0 installed a Windows service with an unquoted executable path containing spaces. This allowed Windows to interpret path components as separate executables, enabling an attacker with local write access to place a malicious binary in an intermediate directory that would execute with SYSTEM privileges when the service starts.
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>= 2022.2.95.0, < 2022.3.186.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Cloudflare Warp is installedOpen Services.msc and look for a service named 'Cloudflare Warp' or check Program Files for Cloudflare Warp installation directoryAffected if The Cloudflare Warp service exists on the system
-
Check installed Warp versionOpen Add or Remove Programs or check the application's version information (right-click the Warp executable, select Properties, go to Details tab)Affected if The installed version is >= 2022.2.95.0 and < 2022.3.186.0
-
Inspect the service binary pathOpen Registry Editor (regedit), navigate to HKLM\SYSTEM\CurrentControlSet\Services\CloudflareWarp, and examine the ImagePath value in the right paneAffected if The ImagePath value contains an unquoted path with spaces (e.g., C:\Program Files\Cloudflare\Warp\warp-svc.exe instead of "C:\Program Files\Cloudflare\Warp\warp-svc.exe")
The system is affected if Cloudflare Warp version is between 2022.2.95.0 and 2022.3.185.0 inclusive and the service registry entry shows an unquoted path with spaces in the ImagePath value.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2022.3.186.0
Upgrade Cloudflare Warp for Windows to version 2022.3.186.0 or later, which properly quotes the service path. Alternatively, manually remediate by ensuring the service binary path in the Windows registry is enclosed in quotes.
2022.3.186.0 or later
- 1. Verify the current installed version of Cloudflare Warp for Windows by checking the application or using system information
- 2. Download Cloudflare Warp version 2023.3.186.0 or later from the official Cloudflare source
- 3. Close any running instances of Cloudflare Warp
- 4. Run the installer for the updated version with appropriate privileges
- 5. Restart the Windows system or the Cloudflare Warp service to ensure the new version is fully operational
- 6. Verify the installed version matches or exceeds 2022.3.186.0 to confirm remediation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2147 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-2147 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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