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.

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

[Snyk] Upgrade @nomiclabs/hardhat-truffle5 from 2.0.2 to 2.0.7 #51

Merged

Conversation

Woodpile37
Copy link
Owner

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


Snyk has created this PR to upgrade @nomiclabs/hardhat-truffle5 from 2.0.2 to 2.0.7.

ℹ️ 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 6 versions ahead of your current version.
  • The recommended version was released a year ago, on 2022-09-02.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Prototype Poisoning
SNYK-JS-QS-3153490
482/1000
Why? Proof of Concept exploit, CVSS 7.5
Proof of Concept
Regular Expression Denial of Service (ReDoS)
SNYK-JS-SEMVER-3247795
482/1000
Why? Proof of Concept exploit, CVSS 7.5
Proof of Concept
Regular Expression Denial of Service (ReDoS)
SNYK-JS-SEMVER-3247795
482/1000
Why? Proof of Concept exploit, CVSS 7.5
Proof of Concept
Prototype Pollution
SNYK-JS-UNSETVALUE-2400660
482/1000
Why? Proof of Concept exploit, CVSS 7.5
No Known Exploit
Prototype Pollution
SNYK-JS-Y18N-1021887
482/1000
Why? Proof of Concept exploit, CVSS 7.5
Proof of Concept
Prototype Pollution
SNYK-JS-JSON5-3182856
482/1000
Why? Proof of Concept exploit, CVSS 7.5
Proof of Concept
Prototype Pollution
SNYK-JS-JSON5-3182856
482/1000
Why? Proof of Concept exploit, CVSS 7.5
Proof of Concept
Regular Expression Denial of Service (ReDoS)
SNYK-JS-UGLIFYJS-1727251
482/1000
Why? Proof of Concept exploit, CVSS 7.5
No Known Exploit
Denial of Service (DoS)
npm:mem:20180117
482/1000
Why? Proof of Concept exploit, CVSS 7.5
No Known Exploit
Cryptographic Issues
SNYK-JS-ELLIPTIC-1064899
482/1000
Why? Proof of Concept exploit, CVSS 7.5
No Known Exploit
Regular Expression Denial of Service (ReDoS)
SNYK-JS-GLOBPARENT-1016905
482/1000
Why? Proof of Concept exploit, CVSS 7.5
Proof of Concept
Open Redirect
SNYK-JS-GOT-2932019
482/1000
Why? Proof of Concept exploit, CVSS 7.5
No Known Exploit
Open Redirect
SNYK-JS-GOT-2932019
482/1000
Why? Proof of Concept exploit, CVSS 7.5
No Known Exploit
Authentication Bypass
SNYK-JS-HTTPAUTH-471683
482/1000
Why? Proof of Concept exploit, CVSS 7.5
No Known Exploit
Prototype Pollution
SNYK-JS-JSON5-3182856
482/1000
Why? Proof of Concept exploit, CVSS 7.5
Proof of Concept

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

Release notes
Package name: @nomiclabs/hardhat-truffle5
  • 2.0.7 - 2022-09-02
  • 2.0.7-rc.0 - 2022-08-31
  • 2.0.6 - 2022-05-11
  • 2.0.5 - 2022-03-01
  • 2.0.4 - 2022-02-10
  • 2.0.3 - 2021-12-09
  • 2.0.2 - 2021-09-30

    This release forbids our async matchers from being chained. This means that you can't do something like:

    await expect(contract.f())
      .to.changeEtherBalance(...)
      .and.to.changeTokenBalance(...)

    This never worked properly, leading to potential false positives in tests. Now this pattern will throw an error to make it clear that it's not supported.

    If some of your tests start throwing because of this, the way to do the same thing without chaining is:

    const tx = contract.f();

    await expect(tx).to.changeEtherBalance(...);
    await expect(tx).to.changeTokenBalance(...);




from @nomiclabs/hardhat-truffle5 GitHub release notes


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

@changeset-bot
Copy link

changeset-bot bot commented Aug 21, 2023

⚠️ No Changeset found

Latest commit: 28984ea

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@Woodpile37 Woodpile37 merged commit c4e2064 into release-v4.5 Aug 21, 2023
1 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants