SSRF (Server-Side Request Forgery) in miniflare (CVE-2023-7078)
Summary
SSRF in miniflare (CVE-2023-7078). Confidential information can be exposed externally. Exploitable via wrangler. Mitigation: upgrade to 3.20231030.2 or later.
Original description
The description as published by the source.
Impact
Sending specially crafted HTTP requests to Miniflare's server could result in arbitrary HTTP and WebSocket requests being sent from the server. If Miniflare was configured to listen on external network interfaces (as was the default in wrangler until 3.19.0), an attacker on the local network could access other local servers.
Patches
The issue was fixed in miniflare@3.20231030.2.
Workarounds
Ensure Miniflare is configured to listen on just local interfaces. This is the default behaviour, but can also be configured with the host: "127.0.0.1" option.
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-7078 has been found in miniflare.
Attackers can target a specific entry point like wrangler over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade miniflare to 3.20231030.2 or later.
If unsure, ask your IT team or search "miniflare CVE-2023-7078" on the vendor's site.
CVE-2023-7078 (miniflare) — CWE-918
Attack vector: adjacent-network / unauthenticated
Attack surface: wrangler
Patched: 3.20231030.2 — apply immediately
Workaround: Ensure Miniflare is configured to listen on just local interfaces.
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.
SSRF (CWE-918) exists in miniflare. Attackers reach the vulnerable code path via wrangler without authentication.
Check the vendor advisory for the affected versions of miniflare. Attack surface: wrangler.
Severity: ?. Confidential information can be exposed externally.
Update to 3.20231030.2.
Workaround: Ensure Miniflare is configured to listen on just local interfaces.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'miniflare' . 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 'miniflare' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
miniflareを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Ensure Miniflare is configured to listen on just local interfaces.パッチが適用されるまでの応急処置として、Ensure Miniflare is configured to listen on just local interfaces. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade miniflare to 3.20231030.2ステージング環境で 3.20231030.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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