WARP: Improper Access Control
CVE-2022-2225 is a high-severity improper access control vulnerability in WARP from Cloudflare, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 2022.5.341.0, 2022.5.346, 2022.5.227.0 as the first without the flaw, so updating WARP to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.19% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update WARP to 2022.5.341.0 or 2022.5.346 or 2022.5.227.0, whichever matches your release line, or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Cloudflare | WARP | before 2022.5.341.0; before 2022.5.346; before 2022.5.227.0 | 2022.5.341.0, 2022.5.346, 2022.5.227.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.1 | High | CNA (cloudflare.com) |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
By using warp-cli subcommands (disable-ethernet, disable-wifi), it was possible for a user without admin privileges to bypass configured Zero Trust security policies (e.g. Secure Web Gateway policies) and features such as 'Lock WARP switch'.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Access Control
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Advisories
- github.com/cloudflare/advisories/security/advisories/GHSA-cg88-vx48-976cThird Party Advisory
Other vulnerabilities in WARP
- 7.1 High severity
- 7.3 High severity
- 7.8 High severity
- 7.8 High severity
- 8.0 High severity
- 8.8 High severity
Recent Improper Access Control vulnerabilities
- 8.8 High severity
- 7.5 High severity
- 8.8 High severity
- 8.1 High severity
- 10.0 Critical severity
- 7.5 High severity
Spotted an error? Tell us.