[Snyk] Upgrade ethereumjs-util from 5.2.1 to 7.1.5

[Boomtokn]

Snyk has created this PR to upgrade ethereumjs-util from 5.2.1 to 7.1.5.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

• The recommended version is 21 versions ahead of your current version.

• The recommended version was released 3 years ago.

Release notes

Package name: ethereumjs-util

• 7.1.5 - 2022-06-03
• 7.1.4 - 2022-02-01
• 7.1.3 - 2021-10-14
• 7.1.2 - 2021-09-29
• 7.1.1 - 2021-09-27
• 7.1.0 - 2021-07-08
• 7.0.10 - 2021-04-01
• 7.0.9 - 2021-03-04
• 7.0.8 - 2021-02-02
• 7.0.7 - 2020-10-19
• 7.0.6 - 2020-10-08
• 7.0.5 - 2020-09-10
• 7.0.4 - 2020-08-04
• 7.0.3 - 2020-07-08
• 7.0.2 - 2020-05-26
• 7.0.1 - 2020-05-15
• 7.0.0 - 2020-04-30
• 6.2.1 - 2020-07-16
  

  Other Features

  • Stricter prefixed hex typing, PRs #3348, #3427 and #3357 (some changes removed in PR #3382 for backwards compatibility reasons, will be reintroduced along upcoming breaking releases)

  Bugfixes

  • Fixes an issue in the delete operation used for unhashed tries and pruning activated which resulted in a wrong state root (bad!), PR #3333
• 6.2.0 - 2019-11-07
• 6.1.0 - 2019-02-12
• 6.0.0 - 2018-10-10
• 5.2.1 - 2020-07-16

from ethereumjs-util GitHub release notes

---

Important

• Warning: This PR contains a major version upgrade, and may be a breaking change.
• Check the changes in this PR to ensure they won't cause issues with your project.
• 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 upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[Boomtokn]

⛔ Snyk checks have failed. 5 issues have been found so far.

Icon	Severity	Issues
	Critical	2
	High	3
	Medium	0
	Low	0

⛔ security/snyk check is complete. 5 issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

[socket-security]

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/ethereumjs-util@7.1.5	None	+16	3.83 MB	holgerd77

🚮 Removed packages: npm/mocha@5.2.0, npm/truffle@4.1.17, npm/web3-provider-engine@14.2.1, npm/web3@0.20.7

View full report↗︎

[socket-security]

🚨 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	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	⚠︎

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