CVE-2022-3337
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 for a user to delete a VPN profile from WARP mobile client on iOS platform despite the Lock WARP switch https://developers.cloudflare.com/cloudflare-one/connections/connect-devices/warp/warp-settings/#lock-warp-switch feature being enabled on Zero Trust Platform. This led to bypassing policies and restrictions enforced for enrolled devices 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 client failed to enforce the Lock WARP switch policy, allowing users to delete VPN profiles even when this administrative control was enabled in Cloudflare Zero Trust. This bypassed device enrollment policies and security restrictions intended for managed devices.
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.15CVSS 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
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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.
-
Identify WARP iOS client installationOn the iOS device, go to Settings > General > VPN & Device Management to check if a Cloudflare WARP VPN profile is installed, or look for the Cloudflare WARP app in the Applications list.Affected if A Cloudflare WARP VPN profile exists on the device.
-
Check WARP iOS client versionOpen the Cloudflare WARP app on the iOS device, navigate to Settings > About, or check the version displayed on the app main screen. Compare the version number to the affected range: versions before 6.15.Affected if The installed WARP iOS client version is lower than 6.15.
-
Verify Lock WARP switch policy configurationIn the Cloudflare Zero Trust dashboard, navigate to Settings > WARP Client > Device settings. Check if the 'Lock WARP switch' policy is enabled for the device enrollment policy.Affected if The Lock WARP switch policy is enabled in Cloudflare Zero Trust.
-
Test VPN profile deletion bypassAttempt to delete the WARP VPN profile from the iOS device (Settings > VPN > select the WARP configuration > Delete VPN Configuration). Observe whether the deletion succeeds despite the Lock WARP switch policy being enabled.Affected if The VPN profile can be successfully deleted while the Lock WARP switch policy is enabled, indicating the bypass is present.
The environment is affected if the WARP iOS client version is below 6.15 AND the Lock WARP switch policy is enabled in Cloudflare Zero Trust, allowing users to delete the VPN profile despite administrative controls.
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.15
Await the Cloudflare vendor patch for the WARP iOS client; in the interim, consider additional mobile device management controls or restrict iOS device enrollment until the fix is available.
Warp Mobile Client version 6.15 or later
- Upgrade Warp Mobile Client for iOS to version 6.15 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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 $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3337 — 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-3337 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