Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2023-7080

Privilege Escalation in wrangler (CVE-2023-7080)

Summary

Vulnerability in wrangler (CVE-2023-7080). Confidential information can be exposed externally. Exploitable via Origin. Mitigation: upgrade to 2.20.2 or later.

Original description

The description as published by the source.

Impact

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.

Patches

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 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.

Workarounds

Unfortunately, Wrangler doesn't provide any configuration for which host that inspector server should listen on. Please upgrade to at least wrangler@3.16.0, and configure Wrangler to listen on local interfaces instead with wrangler dev --ip 127.0.0.1 to prevent SSRF. This removes the local network as an attack vector, but does not prevent an attack from visiting a malicious we…

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2023-7080 has been found in wrangler.
Attackers can target a specific entry point like Origin over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade wrangler to 2.20.2 or later.
If unsure, ask your IT team or search "wrangler CVE-2023-7080" on the vendor's site.

CVE-2023-7080 (wrangler) — CWE-269
Attack vector: adjacent-network / unauthenticated / no user interaction
Attack surface: Origin / Host / miniflare
Patched: 2.20.2 — apply immediately
Workaround: Unfortunately, Wrangler doesn't provide any configuration for which host that inspector server should listen on.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-269) exists in wrangler. Attackers reach the vulnerable code path via Origin without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of wrangler. Attack surface: Origin / Host / miniflare.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 2.20.2.

🛡️ Workaround

Workaround: Unfortunately, Wrangler doesn't provide any configuration for which host that inspector server should listen on.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'wrangler' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'wrangler' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で wrangler を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    Unfortunately, Wrangler doesn't provide any configuration for which host that inspector server should listen on.

    パッチが適用されるまでの応急処置として、Unfortunately, Wrangler doesn't provide any configuration for which host that inspector server should listen on. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade wrangler to 2.20.2

    ステージング環境で 2.20.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm wrangler
[{"type":"SEMVER","events":[{"introduced":"2.0.0"},{"fixed":"2.20.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details