CVE-2023-0238
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 · uneditedDue to lack of a security policy, the WARP Mobile Client (<=6.29) for Android was susceptible to this vulnerability which allowed a malicious app installed on a victim's device to exploit a peculiarity in an Android function, wherein under certain conditions, the malicious app could dictate the task behaviour of the WARP app.
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 confidenceThe WARP Mobile Client for Android (versions up to 6.29) lacks a security policy, allowing a malicious app installed on the same device to exploit a peculiarity in an Android function. This enables the malicious app to dictate task behavior of the WARP app through improper inter-app communication handling.
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.29CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Cloudflare Warp Android app is installedOpen Android Settings > Apps > Find 'Cloudflare Warp' or 'WARP' in the app list, or run: adb shell pm list packages | grep -i warpAffected if The app is present on the device
-
Check installed Warp app versionGo to Settings > Apps > Cloudflare Warp > App info > Version (or Version code), or use: adb shell dumpsys package com.cloudflare.warp | grep versionNameAffected if Version name is lower than 6.29 or version code is below 629000 (indicating version < 6.29)
-
Identify exported app components vulnerable to abuseRun: adb shell dumpsys package com.cloudflare.warp | grep -E 'Export|: exported' to list components (activities, services, receivers) with exported=trueAffected if Any activity, service, or broadcast receiver is exported without proper permission protection, allowing other apps to send intents to Warp
-
Check for Intent Filtering on sensitive componentsReview the AndroidManifest.xml of the Warp app (via decompilation) or run: adb shell dumpsys package com.cloudflare.warp to identify components with intent-filter declarationsAffected if Intent filters are present on components that handle sensitive operations without package verification or input validation
You are affected if Cloudflare Warp Android app version below 6.29 is installed and the app exposes exported components with intent filters that lack security policies for inter-app communication validation.
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.29
Implement a comprehensive security policy in the WARP Android app to validate and restrict how other apps can interact with it, including proper intent filtering, package verification, and input validation for inter-process communication.
WARP Mobile Client for Android version 6.29 or later
- Open the Google Play Store on your Android device
- Search for "Cloudflare WARP" or "1.1.1.1","Update the application to version 6.29 or later
- Alternatively, download the latest version from the official Cloudflare 1.1.1.1 website
- Verify the installed version in the app settings to confirm the update was successful
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0238 — 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-2023-0238 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