CVE-2022-3321
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 · uneditedIt was possible to bypass Lock WARP switch feature https://developers.cloudflare.com/cloudflare-one/connections/connect-devices/warp/warp-settings/#lock-warp-switch on the WARP iOS mobile client by enabling both "Disable for cellular networks" and "Disable for Wi-Fi networks" switches at once in the application settings. Such configuration caused the WARP client to disconnect and allowed the user to bypass restrictions and policies enforced by the Zero Trust platform.
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 confidenceThe WARP iOS mobile client's Lock WARP switch feature could be bypassed by simultaneously enabling both 'Disable for cellular networks' and 'Disable for Wi-Fi networks' switches in the application settings. This configuration forced the WARP client to disconnect, allowing users to bypass restrictions and policies enforced by the Cloudflare Zero Trust platform.
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< 6.14CVSS 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
- None
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
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.
-
Check if WARP iOS client is in use in your organizationReview your Cloudflare Zero Trust dashboard to identify enrolled iOS devices running the WARP client. Navigate to the Devices > Inventory section to list active WARP clients and filter by iOS platform.Affected if Your organization has iOS devices enrolled with the Cloudflare WARP client.
-
Identify the installed WARP iOS client versionIn the Cloudflare Zero Trust dashboard, go to Devices > Inventory and check the client version column for iOS devices. Alternatively, on each iOS device, open the WARP app and navigate to Settings > About to view the build version.Affected if The installed WARP iOS client version is lower than 6.14.
-
Verify if Lock WARP is enforced in your Zero Trust policyIn the Cloudflare Zero Trust dashboard, navigate to Settings > Network > Firewall and locate the Lock WARP setting. Alternatively, check your Gateway network policy rules for any 'Lock WARP' or 'WARP lock' enforcement configurations.Affected if Lock WARP is enabled and enforced in your Zero Trust configuration.
-
Check for WARP disconnection events in logsIn the Cloudflare Zero Trust dashboard, go to Logs > Gateway > Network and filter for events where the connection status shows disconnected or where the action is 'dropped' related to WARP clients. Look for patterns where iOS devices repeatedly disconnect and reconnect.Affected if iOS devices are experiencing unexpected disconnection events that may indicate the bypass was attempted.
-
Review device compliance status for iOS WARP clientsIn the Cloudflare Zero Trust dashboard, navigate to Settings > WARP > Device posture and check the compliance status of iOS devices. Look for devices that show as non-compliant or have recently changed compliance status.Affected if iOS devices running vulnerable WARP versions show as non-compliant or have altered their compliance status after the Lock WARP bypass was triggered.
Your organization is affected if you have iOS devices with WARP client versions below 6.14 and have Lock WARP enforced in your Zero Trust policy, as users on those devices can bypass WARP restrictions by enabling both network disable options.
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 · scoped6.14
This client-side vulnerability requires a fix in the WARP iOS application to prevent the Lock WARP switch bypass when both network disable options are enabled. Organizations should monitor for suspicious network configuration changes and consider additional enforcement mechanisms until the client is patched.
Warp Mobile Client version 6.14 or later
- Open the App Store on your iOS device
- Search for "Cloudflare WARP" or "1.1.1.1" in the App Store
- Tap the Update button next to Cloudflare WARP to install version 6.14 or later
- After updating, verify the Lock WARP switch cannot be bypassed by attempting to enable both "Disable for cellular networks" and "Disable for Wi-Fi networks" simultaneously - the restrictions should now be enforced
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3321 — 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-3321 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