Warp Mobile ClientApplication · Cloudflare

CVE-2022-3322

HIGH · 7.5 CVSS v3.1 Published 2022-10-28
Fix available
A fix is available. Upgrade to 6.14 or later.
See remediation →
84/100
Remediation priority · High
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
Lock Warp switch is a feature of Zero Trust platform which, when enabled, prevents users of enrolled devices from disabling WARP client. Due to insufficient policy verification by WARP iOS client, this feature could be bypassed by using the "Disable WARP" quick action.

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

This is a security feature bypass vulnerability in the Cloudflare WARP iOS client. The 'Lock Warp' feature, designed to prevent users on enrolled devices from disabling the WARP client, can be bypassed by using the 'Disable WARP' quick action due to insufficient policy verification in the iOS client.

MitigationThe vulnerability requires a fix in the WARP iOS client to implement proper policy verification that enforces the Lock Warp setting and prevents the quick action bypass. Organizations should ensure WARP clients are updated once the patch is available.

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
Warp Mobile ClientApplication
Affected:< 6.14

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
None
Integrity
High
Availability
None

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

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 iOS platform
    Verify the device is running iOS (check system settings > About or use 'uname' command output)
    Affected if The device is NOT running iOS - this vulnerability only affects the iOS WARP client
  2. Identify WARP client version
    Open the Cloudflare WARP app, go to Settings > About, or check the iOS App Store app listing for the installed version number
    Affected if The installed version is lower than 6.14 (e.g., 6.13, 6.12, etc.)
  3. Verify Lock Warp is configured
    Check the MDM profile or management policy applied to the device for the Lock Warp or 'warp_lock' setting - this is typically enforced via MDM/MDM-like device management
    Affected if Lock Warp is enabled in the applied policy (the bypass allows disabling WARP despite this setting being active)
  4. Test Disable WARP quick action
    On iOS, access the Disable WARP quick action (typically available via long-press on the WARP app icon or Control Center tile) and attempt to disable WARP while Lock Warp is supposed to be enforced
    Affected if WARP disables successfully via the quick action despite Lock Warp being enabled - this confirms the bypass is present

A user is affected if they are on iOS with Cloudflare WARP client version below 6.14 and have Lock Warp enabled in their MDM policy, allowing the Disable WARP quick action to bypass the lock.

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 6.14 or later
Fixed in 6.14
Interim mitigation

The vulnerability requires a fix in the WARP iOS client to implement proper policy verification that enforces the Lock Warp setting and prevents the quick action bypass. Organizations should ensure WARP clients are updated once the patch is available.

Recommended fix Moderate confidence

Version 6.14 or later

  1. 1. Open the Warp Mobile Client (iOS) on the enrolled device
  2. 2. Navigate to the application settings or preferences
  3. 3. Check the current installed version of the Warp client
  4. 4. If the version is below 6.14, proceed to update the application
  5. 5. Update Warp Mobile Client through the Apple App Store or enterprise mobile device management (MDM) solution
  6. 6. After updating, verify that the "Lock Warp" feature cannot be bypassed using the "Disable WARP" quick action

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

Fix this in Warp Mobile Client Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3322 — 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-2022-3322 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