Path Traversal in wrangler (CVE-2023-3348)
Summary
Path traversal in wrangler (CVE-2023-3348). Confidential information can be exposed externally. Mitigation: upgrade to 2.20.1 or later.
Original description
The description as published by the source.
Impact
The Wrangler command line tool (<=wrangler@3.1.0 or <=wrangler@2.20.1) was affected by a directory traversal vulnerability when running a local development server for Pages (wrangler pages dev command). This vulnerability enabled an attacker in the same network as the victim to connect to the local development server and access the victim's files present outside of the directory for the development server.
Patches
Wrangler2: Upgrade to v2.20.1 or higher.
Wrangler3: Upgrade to v3.1.1 or higher.
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-3348 has been found in wrangler.
Confidential information can be exposed externally.
What to do: upgrade wrangler to 2.20.1 or later.
If unsure, ask your IT team or search "wrangler CVE-2023-3348" on the vendor's site.
CVE-2023-3348 (wrangler) — CWE-22
Attack vector: adjacent-network / unauthenticated
Patched: 2.20.1 — apply immediately
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.
Path traversal (CWE-22) exists in wrangler.
Check the vendor advisory for the affected versions of wrangler.
Severity: ?. Confidential information can be exposed externally.
Update to 2.20.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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 patch patch
Upgrade wrangler to 2.20.1ステージング環境で 2.20.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-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 developers.cloudflare.com
- web github.com