# CVE-2023-7080: Arbitrary remote code execution within wrangler dev Workers sandbox

> Attackers on the local network can execute arbitrary code in the wrangler dev sandbox due to an exposed V8 inspector server lacking proper header validation.

- **Severity:** High 8.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-f8mp-x433-5wpf

## What is CVE-2023-7080?

CVE-2023-7080 is a high-severity code injection vulnerability in Cloudflare wrangler, published on 29 Dec 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The V8 inspector intentionally allows arbitrary code execution within the Workers sandbox for debugging. wrangler dev would previously start an inspector server listening on all network interfaces. This would allow an attacker on the local network to connect to the inspector and run arbitrary code. Additionally, the inspector server did not validate Origin/Host headers, granting an attacker that can trick any user on the local network into opening a malicious website the ability to run code. If wrangler dev --remote was being used, an attacker could access production resources if they were bound to the worker.

This issue was fixed in wrangler@3.19.0 and wrangler@2.20.2. Whilst wrangler dev's inspector server listens on local interfaces by default as of wrangler@3.16.0, an  SSRF vulnerability in miniflare https://github.com/cloudflare/workers-sdk/security/advisories/GHSA-fwvg-2739-22v7  (CVE-2023-7078) allowed access from the local network until wrangler@3.18.0. wrangler@3.19.0 and wrangler@2.20.2 introduced validation for the Origin/Host headers.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2023-7080?

4 open source packages ship an affected version, including wrangler. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wrangler` | npm | From 2.0.0 | 2.20.2 |
| `wrangler` | npm | From 2.0.0 | 2.20.2 |
| `wrangler` | npm | From 3.0.0 | 3.19.0 |
| `wrangler` | npm | From 3.0.0 | 3.19.0 |

Products: Cloudflare Wrangler.

## How do I fix CVE-2023-7080?

Upgrade wrangler to a fixed version for your release line: 2.20.2 or 3.19.0.

## Is CVE-2023-7080 being exploited?

There is no known exploitation of CVE-2023-7080 in the wild and no public exploit code.

## Other vulnerabilities in Cloudflare wrangler

- [CVE-2026-0933](https://insights.sbomify.com/CVE-2026-0933/): OS Command Injection in `wrangler pages deploy` (high 7.7)
- [CVE-2023-7079](https://insights.sbomify.com/CVE-2023-7079/): Arbitrary remote file read in Wrangler dev server (medium 6.4)
- [CVE-2023-3348](https://insights.sbomify.com/CVE-2023-3348/): Directory traversal vulnerability in Cloudflare Wrangler (medium 5.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-7080 and fix it if it is affected.

What it is: CVE-2023-7080 is a high-severity code injection vulnerability in Cloudflare wrangler, published on 29 Dec 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-7080 in the wild and no public exploit code.

Affected packages and fixed versions:
- wrangler (npm): affected from 2.0.0; fixed in 2.20.2
- wrangler (npm): affected from 2.0.0; fixed in 2.20.2
- wrangler (npm): affected from 3.0.0; fixed in 3.19.0
- wrangler (npm): affected from 3.0.0; fixed in 3.19.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-7080/ (Markdown: https://insights.sbomify.com/CVE-2023-7080/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-7080
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-7080
- OSV: https://osv.dev/vulnerability/CVE-2023-7080

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-7080/
Summaries are generated and may contain mistakes; the official description above is the record.