Skip to content

🚨 [security] Update chai 4.2.0 → 4.5.0 (minor) #140

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
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

🚨 [security] Update chai 4.2.0 → 4.5.0 (minor) #140

wants to merge 1 commit into from

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented Jul 26, 2024

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ chai (4.2.0 → 4.5.0) · Repo · Changelog

Release Notes

4.5.0

v4.4.1...v4.5.0

What's Changed

Full Changelog: v4.4.1...v4.5.0

4.4.1

What's Changed

Full Changelog: v4.4.0...v4.4.1

4.3.10

This release simply bumps all dependencies to their latest non-breaking versions.

What's Changed

Full Changelog: v4.3.9...v4.3.10

4.3.9

Upgrade dependencies.

This release upgrades dependencies to address CVE-2023-43646 where a large function name can cause "catastrophic backtracking" (aka ReDOS attack) which can cause the test suite to hang.

Full Changelog: v4.3.8...v4.3.9

4.3.8

What's Changed

New Contributors

Full Changelog: v4.3.7...v4.3.8

4.3.7

What's Changed

  • fix: deep-eql bump package to support symbols comparison by @snewcomer in #1483

Full Changelog: v4.3.6...v4.3.7

4.3.6

Update loupe to 2.3.1

4.3.5

v4.3.4...v4.3.5

4.3.4

This fixes broken inspect behavior with bigints (#1321) (#1383) thanks @vapier

4.3.3

This reintroduces Assertion as an export in the mjs file. See #1378 & #1375

4.3.1

This releases fixed an engine incompatibility with 4.3.0

The 4.x.x series of releases will be compatible with Node 4.0. Please report any errors found in Node 4 as bugs, and they will be fixed.

The 5.x.x series, when released, will drop support for Node 4.0

This fix also ensures pathval is updated to 1.1.1 to fix CVE-2020-7751

4.3.0

This is a minor release.

Not many changes have got in since the last release but this one contains a very important change (#1257) which will allow jest users to get better diffs. From this release onwards, jest users will be able to see which operator was used in their diffs. The operator is a property of the AssertionError thrown when assertions fail. This flag indicates what kind of comparison was made.

This is also an important change for plugin maintainers. Plugin maintainers will now have access to the operator flag, which they can have access to through an utilmethod calledgetOperator`.

Thanks to all the amazing people that contributed to this release.

New Features

  • Allow contain.oneOf to take an array of possible values (@voliva)
  • Adding operator attribute to assertion error (#1257) (@rpgeeganage)
  • The closeTo error message will now inform the user when a delta is required (@eouw0o83hf)

Docs

  • Add contains flag to oneOf documentation (@voliva)

Tests

  • Make sure that useProxy config is checked in overwriteProperty (@vieiralucas)
  • Add tests for contain.oneOf (@voliva )

Chores

  • Update mocha to version 6.1.4
  • Add node v10 and v12 to ci (@vieiralucas)
  • Drop support for node v4, v6 and v9 (@vieiralucas)
  • Fix sauce config for headless chrome (@meeber)
  • Update dev dependencies (@meeber)
  • Removed phantomjs dependency (#1204)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ check-error (indirect, 1.0.2 → 1.0.3) · Repo

Commits

See the full diff on Github. The new version differs by 8 commits:

↗️ deep-eql (indirect, 3.0.1 → 4.1.4) · Repo

Commits

See the full diff on Github. The new version differs by 36 commits:

↗️ get-func-name (indirect, 2.0.0 → 2.0.2) · Repo

Security Advisories 🚨

🚨 Chaijs/get-func-name vulnerable to ReDoS

The current regex implementation for parsing values in the module is susceptible to excessive backtracking, leading to potential DoS attacks. The regex implementation in question is as follows:

const functionNameMatch = /\s*function(?:\s|\s*\/\*[^(?:*/)]+\*\/\s*)*([^\s(/]+)/;

This vulnerability can be exploited when there is an imbalance in parentheses, which results in excessive backtracking and subsequently increases the CPU load and processing time significantly. This vulnerability can be triggered using the following input:

'\t'.repeat(54773) + '\t/function/i'

Here is a simple PoC code to demonstrate the issue:

const protocolre = /\sfunction(?:\s|\s/*[^(?:*\/)]+*/\s*)*([^\(\/]+)/;

const startTime = Date.now();

const maliciousInput = '\t'.repeat(54773) + '\t/function/i'


protocolre.test(maliciousInput);


const endTime = Date.now();


console.log("process time: ", endTime - startTime, "ms");

Commits

See the full diff on Github. The new version differs by 29 commits:

↗️ pathval (indirect, 1.1.0 → 1.1.1) · Repo · Changelog

Security Advisories 🚨

🚨 Prototype pollution in pathval

A prototype pollution vulnerability affects all versions of package pathval under 1.1.1.

Release Notes

1.1.1

Fixes a security issue around prototype pollution.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 12 commits:

↗️ type-detect (indirect, 4.0.8 → 4.1.0) · Repo

Release Notes

4.1.0

What's Changed

New Contributors

Full Changelog: v4.0.9...v4.1.0

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 18 commits:

🆕 loupe (added, 2.3.7)

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added the depfu label Jul 26, 2024
@depfu depfu bot mentioned this pull request Jul 26, 2024
Closed
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

depfu

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant