[Snyk] Fix for 22 vulnerabilities

[lostinauth0]

Snyk has created this PR to fix 22 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

• package.json
• yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Uninitialized Memory Exposure npm:http-proxy-agent:20180406	796
	Uninitialized Memory Exposure npm:https-proxy-agent:20180402	796
	Server-side Request Forgery (SSRF) SNYK-JS-IP-6240864	751
	Uninitialized Memory Exposure npm:base64url:20180511	741
	Prototype Pollution SNYK-JS-LODASH-567746	731
	Remote Code Execution (RCE) SNYK-JS-PACRESOLVER-1564857	726
	Server-side Request Forgery (SSRF) SNYK-JS-NETMASK-1089716	706
	Server-side Request Forgery (SSRF) SNYK-JS-NETMASK-6056519	706
	Prototype Pollution SNYK-JS-LODASH-6139239	696
	Prototype Poisoning SNYK-JS-QS-3153490	696
	Regular Expression Denial of Service (ReDoS) SNYK-JS-SEMVER-3247795	696
	Prototype Pollution SNYK-JS-LODASH-450202	686
	Prototype Pollution SNYK-JS-LODASH-608086	686
	Prototype Pollution SNYK-JS-LODASH-73638	686
	Prototype Pollution SNYK-JS-Y18N-1021887	686
	Code Injection SNYK-JS-LODASH-1040724	681
	Server-Side Request Forgery (SSRF) SNYK-JS-IP-7148531	646
	Prototype Pollution SNYK-JS-JSONSCHEMA-1920922	644
	Man-in-the-Middle (MitM) SNYK-JS-HTTPSPROXYAGENT-469131	626
	Regular Expression Denial of Service (ReDoS) SNYK-JS-LODASH-1018905	586
	Prototype Pollution npm:extend:20180424	579
	Regular Expression Denial of Service (ReDoS) SNYK-JS-LODASH-73639	541

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Server-side Request Forgery (SSRF)
🦉 Prototype Pollution
🦉 Regular Expression Denial of Service (ReDoS)
🦉 More lessons are available in Snyk Learn

[semgrepcode-auth0]

Risk: Affected versions of jsonwebtoken are vulnerable to Use Of A Broken Or Risky Cryptographic Algorithm. The library could be misconfigured so that legacy, insecure key types are used for signature verification. For example, DSA keys could be used with the RS256 algorithm.

Manual Review Advice: A vulnerability from this advisory is reachable if you are using a legacy, insecure key type with a supported algorithm; for example, DSA keys could be used with the RS256 algorithm

Fix: Upgrade this library to at least version 9.0.0 at auth0-account-link-extension/yarn.lock:4710.

Reference(s): GHSA-8cf7-32gw-wr33, CVE-2022-23539

_{Ignore this finding from ssc-30d12dd5-94ad-46fa-9d32-3d5477d86f3e.}

[semgrepcode-auth0]

Risk: Affected versions of jsonwebtoken are vulnerable to Use Of A Broken Or Risky Cryptographic Algorithm. The library could be misconfigured so that legacy, insecure key types are used for signature verification. For example, DSA keys could be used with the RS256 algorithm.

Manual Review Advice: A vulnerability from this advisory is reachable if you are using a legacy, insecure key type with a supported algorithm; for example, DSA keys could be used with the RS256 algorithm

Fix: Upgrade this library to at least version 9.0.0 at auth0-account-link-extension/yarn.lock:4671.

Reference(s): GHSA-8cf7-32gw-wr33, CVE-2022-23539

_{Ignore this finding from ssc-30d12dd5-94ad-46fa-9d32-3d5477d86f3e.}

[semgrepcode-auth0]

Risk: Affected versions of jsonwebtoken are vulnerable to Improper Authentication. Insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC.

Manual Review Advice: A vulnerability from this advisory is reachable if you are using a poorly implemented key retrieval function and your application is supporting usage of both symmetric key and asymmetric key in jwt.verify() implementation with the same key retrieval function.

Fix: Upgrade this library to at least version 9.0.0 at auth0-account-link-extension/yarn.lock:4710.

Reference(s): GHSA-hjrf-2m68-5959, CVE-2022-23541

_{Ignore this finding from ssc-1676dcdc-09e4-4f68-8fa8-5ff232a5b53f.}

[semgrepcode-auth0]

Risk: Affected versions of jsonwebtoken are vulnerable to Improper Authentication. Insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC.

Manual Review Advice: A vulnerability from this advisory is reachable if you are using a poorly implemented key retrieval function and your application is supporting usage of both symmetric key and asymmetric key in jwt.verify() implementation with the same key retrieval function.

Fix: Upgrade this library to at least version 9.0.0 at auth0-account-link-extension/yarn.lock:4671.

Reference(s): GHSA-hjrf-2m68-5959, CVE-2022-23541

_{Ignore this finding from ssc-1676dcdc-09e4-4f68-8fa8-5ff232a5b53f.}