[Snyk] Upgrade web3 from 1.6.1 to 1.10.4

[julitabarelkowska]

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

Snyk has created this PR to upgrade web3 from 1.6.1 to 1.10.4.

ℹ️ 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.

---

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

• The recommended version was released 3 months ago, on 2024-02-05.

The recommended version fixes:

Severity	Issue	PriorityScore (*)	Exploit Maturity
	Regular Expression Denial of Service (ReDoS) SNYK-JS-ES5EXT-6095076	484/1000 Why? Has a fix available, CVSS 5.4	Proof of Concept
	Prototype Pollution SNYK-JS-AXIOS-6144788	484/1000 Why? Has a fix available, CVSS 5.4	No Known Exploit
	Open Redirect SNYK-JS-GOT-2932019	484/1000 Why? Has a fix available, CVSS 5.4	No Known Exploit
	Open Redirect SNYK-JS-GOT-2932019	484/1000 Why? Has a fix available, CVSS 5.4	No Known Exploit
	Regular Expression Denial of Service (ReDoS) SNYK-JS-HTTPCACHESEMANTICS-3248783	484/1000 Why? Has a fix available, CVSS 5.4	Proof of Concept
	Prototype Pollution SNYK-JS-MINIMIST-2429795	484/1000 Why? Has a fix available, CVSS 5.4	Proof of Concept

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

Release notes

Package name: web3

• 1.10.4 - 2024-02-05
  

  Security

  • Updated dependencies (#6731)

  ---

  Maintenance Countdown:

  Commencing from January 1, 2024, a 90-day countdown has been initiated, signaling the transition of Web3.js version 1.x into an end-of-maintenance phase.

  Timeline of Changes:

  90-Day Countdown (1/1/24 - 3/31/24): During this period, we strongly encourage users to plan accordingly and initiate the upgrade to Web3.js version 4.x

  No New Bug Fixes (4/1/24 onwards):

  Starting April 1, 2024, new bug fixes for Web3.js version 1.x will no longer be provided. To benefit from continued support and access to new features, we recommend upgrading to Web3.js version 4.x

  End of Security Fixes (7/1/24):

  Security fixes for Web3.js version 1.x will be discontinued from July 1, 2024. Upgrading to Web3.js version 4.x is crucial to ensure the security of your applications.

• 1.10.4-dev.0 - 2024-01-31
  

  Security

  • Updated dependencies (#6731)
• 1.10.3 - 2023-10-18
• 1.10.3-dev.0 - 2023-10-16
• 1.10.2 - 2023-08-28
• 1.10.1 - 2023-08-14
• 1.10.1-rc.0 - 2023-08-08
• 1.10.0 - 2023-05-10
• 1.10.0-rc.0 - 2023-05-02
• 1.9.0 - 2023-03-20
• 1.9.0-rc.0 - 2023-03-07
• 1.8.2 - 2023-01-30
• 1.8.2-rc.0 - 2023-01-11
• 1.8.1 - 2022-11-10
• 1.8.1-rc.0 - 2022-10-28
• 1.8.0 - 2022-09-14
• 1.8.0-rc.0 - 2022-09-08
• 1.7.5 - 2022-08-01
• 1.7.5-rc.1 - 2022-07-19
• 1.7.5-rc.0 - 2022-07-15
• 1.7.4 - 2022-06-21
• 1.7.4-rc.2 - 2022-06-16
• 1.7.4-rc.1 - 2022-06-08
• 1.7.4-rc.0 - 2022-05-17
• 1.7.3 - 2022-04-08
• 1.7.3-rc.0 - 2022-04-07
• 1.7.2 - 2022-04-07
• 1.7.2-rc.0 - 2022-03-24
• 1.7.1 - 2022-03-03
• 1.7.1-rc.0 - 2022-02-10
• 1.7.0 - 2022-01-17
• 1.7.0-rc.0 - 2021-12-09
• 1.6.1 - 2021-11-15

from web3 GitHub release notes

Commit messages

Package name: web3

• 56d35a4 lerna version bump and build
• 5b1b9d7 version bumps and lerna build
• 4ab6cc4 changelog update
• f5b72a0 npm i and npm audit fix
• 53e01d9 1x libs update (#6731)
• 5b33133 Add 1.x deprecation notice (#6723)
• 0e8695b 1x release process (#6550)
• 926c882 Release/1.10.3 (#6510)
• dbd96ae 1x deps update (#6491)
• aafce59 v1/chore(web3-eth-accounts): bump @ ethereumjs/common and @ ethereumjs/tx (#6457)
• c44abcd Release/1.10.2 (#6382)
• 9e063ef Fixed broken fetch for Node.js > 18.x and fixed double callback (#6381)
• 3e685bf Release/1.10.1 (#6329)
• 1b65ccf codeowners update (#6324)
• d4217a2 1x doc updates (#6325)
• 5f02175 Replace ethereumjs-util with @ ethereumjs/util (#6283)
• e68194b 1.x - update submit work and contract.myMethod.send docs (#6229)
• 47b9769 Fix for ABI encoding large negative ints (#6239)
• 512aba7 Bump `typescript` to `4.9.5` and `ts-node` to `10.9.1` (#6238)
• 6bde558 Release/1.10.0 (#6058)
• 13a2edc Remove the unnecessary chainId parameter (#5888) (#6057)
• 7b3ce91 1x update (#6044)
• 195cd3c Filter option doesn't work in getPastEvents (#6015)
• 48958ee Nicos99/revert call (#6009)

Compare

---

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

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Note: This is a default PR template raised by Snyk. Find out more about how you can customise Snyk PRs in our documentation.

[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/es5-ext@0.10.64	Install script: postinstall Source: node -e "try{require('./_postinstall')}catch(e){}" || exit 0	orphan: npm/es5-ext@0.10.64

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/es5-ext@0.10.64

[coderabbitai]

Important

Auto Review Skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.