Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Snyk] Upgrade: , chai, chai-as-promised, mocha #19

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Snyk] Upgrade: , chai, chai-as-promised, mocha #19

wants to merge 1 commit into from

Conversation

metatrust-v
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade multiple dependencies.

👯‍♂ The following dependencies are linked and will therefore be updated together.

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

Name Versions Released on

@openzeppelin/contracts
from 4.4.1 to 4.9.6 | 26 versions ahead of your current version | 6 months ago
on 2024-02-29
chai
from 4.3.4 to 4.5.0 | 9 versions ahead of your current version | a month ago
on 2024-07-25
chai-as-promised
from 7.1.1 to 7.1.2 | 1 version ahead of your current version | 4 months ago
on 2024-05-11
mocha
from 9.1.3 to 9.2.2 | 4 versions ahead of your current version | 2 years ago
on 2022-03-11

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-GETFUNCNAME-5923417		 751 Proof of Concept
high severity Information Exposure
SNYK-JS-OPENZEPPELINCONTRACTS-2958047		 751 No Known Exploit
high severity Information Exposure
SNYK-JS-OPENZEPPELINCONTRACTS-2958050		 751 No Known Exploit
high severity Incorrect Calculation
SNYK-JS-OPENZEPPELINCONTRACTS-2964946		 751 No Known Exploit
high severity Improper Verification of Cryptographic Signature
SNYK-JS-OPENZEPPELINCONTRACTS-2980279		 751 No Known Exploit
medium severity Improper Input Validation
SNYK-JS-OPENZEPPELINCONTRACTS-5425051		 751 No Known Exploit
medium severity Improper Encoding or Escaping of Output
SNYK-JS-OPENZEPPELINCONTRACTS-5838352		 751 No Known Exploit
medium severity Information Exposure
SNYK-JS-NANOID-2332193		 751 Proof of Concept
medium severity Function Call With Incorrect Argument
SNYK-JS-OPENZEPPELINCONTRACTS-2336323		 751 No Known Exploit
medium severity Denial of Service (DoS)
SNYK-JS-OPENZEPPELINCONTRACTS-2965798		 751 No Known Exploit
low severity Denial of Service (DoS)
SNYK-JS-OPENZEPPELINCONTRACTS-5425827		 751 No Known Exploit
low severity Missing Authorization
SNYK-JS-OPENZEPPELINCONTRACTS-5672116		 751 No Known Exploit
Release notes
Package name: @openzeppelin/contracts
  • 4.9.6 - 2024-02-29
    • Base64: Fix issue where dirty memory located just after the input buffer is affecting the result. (#4929)
  • 4.9.5 - 2023-12-08
    • Multicall: Make aware of non-canonical context (i.e. msg.sender is not _msgSender()), allowing compatibility with ERC2771Context. Patch duplicated Address.functionDelegateCall in v4.9.4 (removed).
  • 4.9.4 - 2023-12-07
    • 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
  • 4.8.0 - 2022-11-08
  • 4.8.0-rc.2 - 2022-10-17
  • 4.8.0-rc.1 - 2022-09-23
  • 4.8.0-rc.0 - 2022-09-07
  • 4.7.3 - 2022-08-10
  • 4.7.2 - 2022-07-27
  • 4.7.1 - 2022-07-20
  • 4.7.0 - 2022-06-29
  • 4.7.0-rc.0 - 2022-06-07
  • 4.6.0 - 2022-04-26
  • 4.6.0-rc.0 - 2022-03-31
  • 4.5.0 - 2022-02-09
  • 4.5.0-rc.0 - 2022-01-13
  • 4.4.2 - 2022-01-11
  • 4.4.1 - 2021-12-14
from @openzeppelin/contracts GitHub release notes
Package name: chai from chai GitHub release notes
Package name: chai-as-promised from chai-as-promised GitHub release notes
Package name: mocha from mocha 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:

@snyk-bot
fix: upgrade multiple dependencies with Snyk
97b3804 
Snyk has created this PR to upgrade:
  - @openzeppelin/contracts from 4.4.1 to 4.9.6.
    See this package in npm: https://www.npmjs.com/package/@openzeppelin/contracts
  - chai from 4.3.4 to 4.5.0.
    See this package in npm: https://www.npmjs.com/package/chai
  - chai-as-promised from 7.1.1 to 7.1.2.
    See this package in npm: https://www.npmjs.com/package/chai-as-promised
  - mocha from 9.1.3 to 9.2.2.
    See this package in npm: https://www.npmjs.com/package/mocha

See this project in Snyk:
https://app.snyk.io/org/wangzhecodingfy/project/f963b27a-0781-41ae-9040-c648ddeeff61?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@metatrust-v @snyk-bot