Update dependency wrangler to v3.51.0 [SECURITY] - abandoned #74
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.50.0
->3.51.0
GitHub Vulnerability Alerts
CVE-2023-3348
Impact
The Wrangler command line tool (<[email protected] or <[email protected]) 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
Workers SDK on Github
Wrangler docs
CVE-2023-3348
CVE-2023-7080
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 validateOrigin
/Host
headers, granting an attacker that can trick any user on the local network into opening a malicious website the ability to run code. Ifwrangler 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]
. Whilstwrangler dev
's inspector server listens on local interfaces by default as of[email protected]
, an SSRF vulnerability inminiflare
allowed access from the local network until[email protected]
.[email protected]
and[email protected]
introduced validation for theOrigin
/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 withwrangler 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
Release Notes
cloudflare/workers-sdk (wrangler)
v3.51.0
Compare Source
Minor Changes
#5477
9a46e03
Thanks @pmiguel! - feature: Changed Queues client to use the new QueueId and ConsumerId-based endpoints.#5172
fbe1c9c
Thanks @GregBrimble! - feat: Allow marking external modules (with--external
) to avoid bundling them when building Pages FunctionsIt's useful for Pages Plugins which want to declare a peer dependency.
Patch Changes
#5585
22f5841
Thanks @geelen! - Updateswrangler d1 export
to handle larger DBs more efficientlyUpdated dependencies [
c9f081a
,c9f081a
]:Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.