📦 Bump versions of multiple dependencies to address vulnerabilities

[fixleftdev]

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

Component	CVE ID	Severity	Description
npm:wrangler:2.1.7	CVE-2023-3348	Medium	### 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
npm:wrangler:2.1.7	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<br>--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 - cloudflare/workers-sdk#4430 - cloudflare/workers-sdk#4437 - cloudflare/workers-sdk#4535 - cloudflare/workers-sdk#4550
npm:undici:5.9.1	CVE-2024-30261	Low	### Impact If an attacker can alter the integrity option passed to fetch(), they can let fetch() accept requests as valid even if they have been tampered. ### Patches Fixed in nodejs/undici@d542b8c. Fixes has been released in v5.28.4 and v6.11.1. ### Workarounds Ensure that integrity cannot be tampered with. ### References https://hackerone.com/reports/2377760
npm:undici:5.9.1	CVE-2024-30260	Low	### Impact Undici cleared Authorization and Proxy-Authorization headers for fetch(), but did not clear them for undici.request(). ### Patches This has been patched in nodejs/undici@6805746. Fixes has been released in v5.28.4 and v6.11.1. ### Workarounds use fetch() or disable maxRedirections. ### References Linzi Shang reported this. * https://hackerone.com/reports/2408074 * GHSA-3787-6prv-h9w3

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

Thank you for reviewing the update! 🚀