[Snyk] Fix for 32 vulnerabilities

snyk-top-banner

Snyk has created this PR to fix 32 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

package.json
package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Server-side Request Forgery (SSRF) SNYK-JS-IP-6240864	751
	Prototype Pollution SNYK-JS-LODASH-567746	731
	Prototype Pollution SNYK-JS-LODASHES-2434283	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-UAPARSERJS-1023599	696
	Regular Expression Denial of Service (ReDoS) SNYK-JS-UAPARSERJS-610226	696
	Prototype Pollution SNYK-JS-LODASH-450202	686
	Prototype Pollution SNYK-JS-LODASH-608086	686
	Prototype Pollution SNYK-JS-LODASHES-2434285	686
	Prototype Pollution SNYK-JS-LODASHES-2434290	686
	Prototype Pollution SNYK-JS-Y18N-1021887	686
	Code Injection SNYK-JS-LODASH-1040724	681
	Code Injection SNYK-JS-LODASHES-2434284	681
	Server-Side Request Forgery (SSRF) SNYK-JS-IP-7148531	646
	Server-side Request Forgery (SSRF) SNYK-JS-REQUEST-3361831	646
	Prototype Pollution SNYK-JS-TOUGHCOOKIE-5672873	646
	Prototype Pollution SNYK-JS-JSONSCHEMA-1920922	644
	Man-in-the-Middle (MitM) SNYK-JS-HTTPSPROXYAGENT-469131	626
	Prototype Pollution SNYK-JS-AJV-584908	619
	Regular Expression Denial of Service (ReDoS) SNYK-JS-UAPARSERJS-1072471	616
	Regular Expression Denial of Service (ReDoS) SNYK-JS-COOKIEJAR-3149984	586
	Regular Expression Denial of Service (ReDoS) SNYK-JS-LODASH-1018905	586
	Regular Expression Denial of Service (ReDoS) SNYK-JS-LODASHES-2434289	586
	Information Exposure SNYK-JS-NODEFETCH-2342118	539
	Denial of Service SNYK-JS-NODEFETCH-674311	520
	Regular Expression Denial of Service (ReDoS) npm:clean-css:20180306	506
	Regular Expression Denial of Service (ReDoS) npm:debug:20170905	506
	Regular Expression Denial of Service (ReDoS) npm:ms:20170412	399

[!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:

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

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Critical CVE	npm/crypto-js@3.3.0	CVE: GHSA-xwcq-pm8m-c4vf crypto-js PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard (CRITICAL) Affected versions: < 4.2.0 Patched version: 4.2.0	`package-lock.json`	⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

@SocketSecurity ignore npm/crypto-js@3.3.0

auth0-extensions / auth0-delegated-administration-extension