[Snyk] Upgrade @openzeppelin/contracts-upgradeable from 4.8.1 to 4.9.6

[ramzimalhas]

Snyk has created this PR to upgrade @openzeppelin/contracts-upgradeable from 4.8.1 to 4.9.6.

ℹ️ 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 11 versions ahead of your current version.

• The recommended version was released on 6 months ago.

Issues fixed by the recommended upgrade:

	Issue	Score	Exploit Maturity
	Incorrect Calculation SNYK-JS-OPENZEPPELINCONTRACTSUPGRADEABLE-3339524	479	No Known Exploit
	Incorrect Calculation SNYK-JS-OPENZEPPELINCONTRACTSUPGRADEABLE-3339526	479	No Known Exploit
	Improper Input Validation SNYK-JS-OPENZEPPELINCONTRACTSUPGRADEABLE-5425052	479	No Known Exploit
	Improper Input Validation SNYK-JS-OPENZEPPELINCONTRACTSUPGRADEABLE-5711903	479	No Known Exploit
	Improper Encoding or Escaping of Output SNYK-JS-OPENZEPPELINCONTRACTSUPGRADEABLE-5838353	479	No Known Exploit
	Out-of-bounds Read SNYK-JS-OPENZEPPELINCONTRACTSUPGRADEABLE-6346764	479	No Known Exploit
	Denial of Service (DoS) SNYK-JS-OPENZEPPELINCONTRACTSUPGRADEABLE-5425826	479	No Known Exploit
	Missing Authorization SNYK-JS-OPENZEPPELINCONTRACTSUPGRADEABLE-5672117	479	No Known Exploit

Release notes

Package name: @openzeppelin/contracts-upgradeable

• 4.9.6 - 2024-02-29
  
  • Base64: Fix issue where dirty memory located just after the input buffer is affecting the result. (#4926)
• 4.9.5 - 2023-12-08
  
  • Multicall: Patch duplicated Address.functionDelegateCall.
• 4.9.4 - 2023-12-08
  
  • ERC2771Context and Context: Introduce a _contextPrefixLength() getter, used to trim extra information appended to msg.data.
  • Multicall: Make aware of non-canonical context (i.e. msg.sender is not _msgSender()), allowing compatibility with ERC2771Context.
• 4.9.3 - 2023-07-28
  

  Note
  This release contains a fix for GHSA-g4vp-m682-qqmp.

  • ERC2771Context: Return the forwarder address whenever the msg.data of a call originating from a trusted forwarder is not long enough to contain the request signer address (i.e. msg.data.length is less than 20 bytes), as specified by ERC-2771. (#4481)
  • ERC2771Context: Prevent revert in _msgData() when a call originating from a trusted forwarder is not long enough to contain the request signer address (i.e. msg.data.length is less than 20 bytes). Return the full calldata in that case. (#4484)
• 4.9.2 - 2023-06-16
• 4.9.1 - 2023-06-07
• 4.9.0 - 2023-05-23
• 4.9.0-rc.1 - 2023-05-17
• 4.9.0-rc.0 - 2023-05-09
• 4.8.3 - 2023-04-13
• 4.8.2 - 2023-03-02
• 4.8.1 - 2023-01-13

from @openzeppelin/contracts-upgradeable GitHub release notes

---

Important

• 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.
• Max score is 1000. Note that the real score may have changed since the PR was raised.

---

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

[height]

Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword link (e.g. "Link T-123").

💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.

[coderabbitai]

Important

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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

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

CodeRabbit Configuration 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.

[elessar-for-github]

Changes made by this pull request:

contract_library/package.json
Updated the version of "@openzeppelin/contracts-upgradeable" from "^4.8.1" to "^4.9.6".