Authentication Bypass in wrangler (CVE-2023-7079)
Summary
Authentication bypass in wrangler (CVE-2023-7079). Confidential information can be exposed externally. Mitigation: upgrade to 3.19.0 or later.
Original description
The description as published by the source.
Impact
Sending specially crafted HTTP requests and inspector messages to Wrangler's dev server could result in any file on the user's computer being accessible over the local network. An attacker that could trick any user on the local network into opening a malicious website could also read any file.
Patches
This issue was fixed in wrangler@3.19.0. Wrangler will now only serve files that are part of your bundle, or referenced by your bundle's source maps.
Workarounds
Configure Wrangler to listen on local interfaces instead with wrangler dev --ip 127.0.0.1. This is the default as of wrangler@3.16.0, and removes the local network as an attack vector, but does not prevent an attack from visiting a malicious website.
References
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-7079 has been found in wrangler.
Confidential information can be exposed externally.
What to do: upgrade wrangler to 3.19.0 or later.
If unsure, ask your IT team or search "wrangler CVE-2023-7079" on the vendor's site.
CVE-2023-7079 (wrangler) — CWE-287
Attack vector: adjacent-network / unauthenticated / no user interaction
Patched: 3.19.0 — apply immediately
Workaround: Configure Wrangler to listen on local interfaces instead with wrangler dev --ip 127.0.0.1.
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.
Authentication bypass (CWE-287) exists in wrangler.
Check the vendor advisory for the affected versions of wrangler.
Severity: ?. Confidential information can be exposed externally.
Update to 3.19.0.
Workaround: Configure Wrangler to listen on local interfaces instead with wrangler dev --ip 127.0.0.1.
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
-
1Identify exposure identify
grep -r 'wrangler' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
wranglerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Configure Wrangler to listen on local interfaces instead with `wrangler dev --ip 127.0.0.1`.パッチが適用されるまでの応急処置として、Configure Wrangler to listen on local interfaces instead with
wrangler dev --ip 127.0.0.1. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade wrangler to 3.19.0ステージング環境で 3.19.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com