📦 Bump npm:wrangler:2.1.7 from 2.1.7 to 2.20.1

[fixleftdev]

Lineaje has automatically created this pull request to resolve the following CVEs:

CVE ID	Severity	Description
CVE-2023-7080	Critical	### 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 [email protected] and [email protected]. Whilst wrangler dev's inspector server listens on local interfaces by default as of [email protected], an SSRF vulnerability in miniflare allowed access from the local network until [email protected]. [email protected] and [email protected] 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 [email protected], 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 website.

References

• 🐛 BUG: Wrangler is still listening on the wildcard address even with --ip localhost cloudflare/workers-sdk#4430
• Change dev registry and inspector server to use 127.0.0.1 instead of all interfaces cloudflare/workers-sdk#4437
• Revert "Revert "startDevWorker - Milestone 1"" cloudflare/workers-sdk#4535
• fix: validate Host/Origin headers in magic proxy and InspectorProxyWorker cloudflare/workers-sdk#4550
  |
  | CVE-2023-7080 | Critical | ### 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 [email protected] and [email protected]. Whilst wrangler dev's inspector server listens on local interfaces by default as of [email protected], an SSRF vulnerability in miniflare allowed access from the local network until [email protected]. [email protected] and [email protected] 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 [email protected], 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 website.

References

• 🐛 BUG: Wrangler is still listening on the wildcard address even with --ip localhost cloudflare/workers-sdk#4430
• Change dev registry and inspector server to use 127.0.0.1 instead of all interfaces cloudflare/workers-sdk#4437
• Revert "Revert "startDevWorker - Milestone 1"" cloudflare/workers-sdk#4535
• fix: validate Host/Origin headers in magic proxy and InspectorProxyWorker cloudflare/workers-sdk#4550
  |

You can merge this PR once the tests pass and the changes are reviewed.

Thank you for reviewing the update! 🚀