[Snyk] Security upgrade @0x/dev-utils from 3.3.6 to 5.0.0

[adamlaska]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • contracts/extensions/package.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	768/1000 Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5	Prototype Pollution SNYK-JS-WEB3UTILS-6229337	Yes	Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: @0x/dev-utils

The new version differs by 193 commits.

• aad2bd4 Publish
• ae6753a Updated CHANGELOGS & MD docs
• 91344c0 Bump CirciCI to nodejs16 ([Snyk] Fix for 5 vulnerabilities #68)
• ae232fa Bump CI to node16
• b89d468 Cannot run installation against specific package ([Snyk] Fix for 5 vulnerabilities #67)
• e003034 fix: Update deps fix ([pull] development from 0xProject:development #65)
• 14e5370 empty
• 27955e3 chore: Update deps ([Snyk] Security upgrade moment from 2.21.0 to 2.29.4 #64)
• 7e7e6dc fix: Fix subprovider tests
• dbd0dc0 bump ts
• 094c081 Bump subprovider deps
• 3c0bb9e Update @ ethereumjs/common
• 9d28e7d Unpin merkle-patricia-tree
• b543924 Add repository to @ 0x/subproviders
• 0787b82 Publish
• c9009bd Updated CHANGELOGS & MD docs
• 136b9dd Merge pull request [Snyk] Security upgrade nyc from 11.9.0 to 14.0.0 #62 from 0xProject/fix/ethereum-types-linkReferences
• c44fb80 make compiler output artifact `linkReferences` optional (for 0.8)
• 41976dd Publish
• e7e2055 Updated CHANGELOGS & MD docs
• 33ae44c Update publish.yml
• 343b40d Merge pull request [Snyk] Security upgrade nyc from 11.9.0 to 14.0.0 #61 from 0xProject/fix/solc-compiler-0.8-support
• b80738e update sol-tracing-utils deps
• 7f28191 appease prettier

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

---

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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Prototype Pollution

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@0x/abi-gen@5.8.5	filesystem, shell Transitive: environment, network	+36	2.48 MB	tobernguyen
npm/@0x/base-contract@6.5.0	Transitive: eval, network	+25	4.93 MB	dorothy-zbornak
npm/@0x/contracts-asset-proxy@3.7.19	None	0	10.1 MB	dorothy-zbornak
npm/@0x/contracts-erc1155@2.1.37	Transitive: network	+4	1.47 MB	dorothy-zbornak
npm/@0x/contracts-erc20@3.3.57	Transitive: eval, network	+14	3.63 MB	tobernguyen
npm/@0x/contracts-erc721@3.1.37	None	0	613 kB	dorothy-zbornak
npm/@0x/contracts-exchange-libs@4.3.37	Transitive: network	+4	1.04 MB	dorothy-zbornak
npm/@0x/contracts-exchange@3.2.38	None	+1	5.29 MB	dorothy-zbornak
npm/@0x/contracts-gen@2.0.51	Transitive: environment, filesystem, network, unsafe	+11	12.2 MB	tobernguyen
npm/@0x/contracts-test-utils@5.4.60	environment Transitive: eval, filesystem, network, shell, unsafe	+128	214 MB	tobernguyen
npm/@0x/contracts-utils@4.8.52	Transitive: eval, network	+13	2.56 MB	tobernguyen
npm/@0x/dev-utils@3.3.6	environment, filesystem Transitive: eval, network, shell, unsafe	+84	17.4 MB	dorothy-zbornak
npm/@0x/sol-compiler@4.8.5	environment, filesystem, network, shell Transitive: eval, unsafe	+35	12.4 MB	tobernguyen
npm/@0x/tslint-config@4.1.5	None	+1	441 kB	dekz
npm/@0x/types@3.3.7	None	+1	443 kB	dekz
npm/@0x/typescript-typings@5.3.2	None	+2	467 kB	dekz
npm/@0x/utils@5.6.4	network	+7	1.37 MB	dorothy-zbornak
npm/@0x/web3-wrapper@7.6.5	Transitive: eval, network	+12	2.14 MB	dorothy-zbornak
npm/ethereum-types@3.7.1	None	+1	409 kB	dekz
npm/ethereumjs-util@7.1.5	None	+3	486 kB	holgerd77
npm/mocha@6.2.3	environment, filesystem	+34	2.44 MB	juergba
npm/tslint@5.11.0	filesystem Transitive: environment	+7	2.86 MB	palantir

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	Source
Install scripts	npm/@0x/subproviders@6.6.5	Install script: postinstall Source: node -e "try{ fs.unlinkSync(path.resolve(path.dirname(require.resolve('ganache-core')), './typings/index.d.ts')) } catch (err) {}"	contracts/asset-proxy/package.json
Install scripts	npm/@0x/subproviders@8.0.1	Install script: postinstall Source: ``	contracts/asset-proxy/package.json

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

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/@0x/subproviders@6.6.5
• @SocketSecurity ignore npm/@0x/subproviders@8.0.1