CVE-2022-3512
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 · uneditedUsing warp-cli command "add-trusted-ssid", a user was able to disconnect WARP client and bypass the "Lock WARP switch" feature resulting in Zero Trust policies not being enforced on an affected 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 confidenceA logic flaw in warp-cli's add-trusted-ssid command allows a local authenticated user to bypass the administrator-enforced 'Lock WARP switch' policy and disconnect the WARP client, thereby disabling Zero Trust network policies on the endpoint.
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.8.857.0< 2022.8.861.0< 2022.8.936CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Identify installed WARP client versionRun 'warp-cli --version' or check the installed package version via system package manager (e.g., 'dpkg -l | grep warp', 'rpm -qi warp', or in Windows check Programs and Features)Affected if The installed version is one of: < 2022.8.857.0, < 2022.8.861.0, or < 2022.8.936 (note: multiple version branches were affected)
-
Verify if WARP client is currently connectedRun 'warp-cli status' and check if the client reports as connected or disconnectedAffected if The client shows as disconnected when it should be connected according to organizational policy
-
Review WARP client logs for unauthorized disconnection eventsCheck WARP client logs (typically in /var/log/warp/ or Windows Event Viewer under Cloudflare WARP logs) for entries containing 'disconnect', 'ssid', or 'add-trusted-ssid' commands around the time of unexpected disconnectionsAffected if Logs show disconnect commands or add-trusted-ssid operations that were not initiated by an administrator
-
Check if Lock WARP switch policy is configuredIn the Cloudflare Zero Trust dashboard, navigate to Settings > WARP Client > Device settings and verify if 'Lock WARP switch' is enabled for the device enrollment policyAffected if The 'Lock WARP switch' policy is enabled, meaning users should not be able to disconnect the client manually
-
Audit recent warp-cli command executionReview system audit logs, bash history, or Windows PowerShell history for recent executions of 'warp-cli add-trusted-ssid' or 'warp-cli disconnect' commands by non-admin usersAffected if Non-administrator users have executed warp-cli commands related to SSID management or disconnection
A defender is affected if they have WARP client version < 2022.8.857.0 (or < 2022.8.861.0 or < 2022.8.936 depending on version branch) installed in an environment where the Lock WARP switch policy should prevent user disconnection.
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.8.857.02022.8.861.02022.8.936
Apply vendor-provided patch/update to WARP client software; until patched, monitor for unauthorized WARP disconnections and consider restricting local CLI access to warp-cli.
WARP version 2022.8.857.0 or later (or 2022.8.861.0/2022.8.936 for specific platforms)
- 1. Identify the current installed version of Cloudflare WARP client on the affected endpoint
- 2. Download the latest version of Cloudflare WARP from the official Cloudflare website or your organization's software distribution point
- 3. Uninstall the current version of WARP or run the installer to upgrade in-place
- 4. Verify the new version is 2022.8.857.0 or later (or the appropriate fixed version for your platform: 2022.8.861.0 or 2022.8.936)
- 5. Confirm the "add-trusted-ssid" command no longer allows bypassing the "Lock WARP switch" feature
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3512 — 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-3512 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