🚨 [security] Upgrade bcrypt: 3.0.6 → 5.0.0 (major)

[depfu]

---

🚨 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 upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ bcrypt (3.0.6 → 5.0.0) · Repo · Changelog

Security Advisories 🚨

🚨 Inadequate Encryption Strength in bcrypt

In bcrypt (npm package) before version 5.0.0, data is truncated wrong when its length is greater than 255 bytes.

Release Notes

5.0.0

• Fix the bcrypt "wrap-around" bug. It affects passwords with lengths >= 255.
  It is uncommon but it's a bug nevertheless. Previous attempts to fix the bug
  was unsuccessful.
• Experimental support for z/OS
• Fix a bug related to NUL in password input
• Update node-pre-gyp to 0.15.0

4.0.1

bcrypt 4.0.1

4.0.0

NAPI support

3.0.8

• Update node-pre-gyp to 0.14
• Pre-built binaries for NodeJS 13

3.0.7

bcrypt 3.0.7

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

Commits

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

• v5.0.0
• Update node-pre-gyp to 0.15.0
• Add NodeJS 14 to appveyor CI
• Merge pull request #807 from techhead/known_length
• Reword comment
• Add test for embedded NULs
• Pass key_len to bcrypt(). Fix for issues #774, #776
• Merge pull request #647 from ilatypov/master
• Allow using an enterprise artifactory.
• Mark z/OS compatibility code as such
• Add z/OS support
• Update CHANGELOG.md
• Merge pull request #806 from techhead/2b_overflow
• Fix overflow bug. See issue #776
• Merge pull request #804 from jokester/add-arm64-build
• add linux-arm64 to build matrix
• Update node-addon-api to v3.0.0
• Use travis to deploy future releases
• v4.0.1
• Prepare for uploading releases from inside docker
• Define _GNU_SOURCE while compiling for MUSL
• Add alpine-linux to CI
• Readme: fix node version for v4.0.0
• Update CHANGELOG.md
• v4.0.0
• Update node-addon-api to v2.0.0
• Minor readme tweaks
• Removed extra spacing.
• Updated to node-addon-api 2.0.0. Handle the error on AsyncQoeker in a different way.
• Drop unsupported Node versions from CI test matrix
• Merge branch 'napi'
• v3.0.8
• Update readme to indicate truncation at 72 bytes.
• Fixed up some confusing language.
• GH-720 - change to strcmp.
• GH-720 - Update readme regarding timing attacks.
• Update nan to 0.14.0
• Merge pull request #763 from anderslatif/master
• Add NodeJS 13 to CI (#762)
• Changed the word used in the documentation from response to result
• Updated the examples to use the word response instead of res to avoid collision
• Add NodeJS 13 to CI
• v3.0.7
• Update dependencies
• Add NodeJS 12 to CI
• Update nan & node-pre-gyp (#743)
• Update nan & node-pre-gyp

✳️ chart.js (2.9.1 → 2.9.3) · Repo

Release Notes

2.9.3

Bug Fixes

• #6698 Fix undefined variable
• #6719 Don't make legend empty when fill is false

Thanks to the maintainers and collaborators for their help to improve and test Chart.js (@kurkle, @benmccann, and @etimberg).

2.9.2

Bug Fixes

• #6641 IE11 & Edge compatible style injection
• #6655 Backwards compatible default fill for radar charts
• #6660 Improve clipping of line charts when border widths are large
• #6661 When a legend item is clicked, make sure the correct item is hidden
• #6663 Refresh package-lock file to pick up new dependency

Performance

• #6671 Stop unnecessary line calculations

Documentation

• #6643 Combine performance documentation sections

Thanks to the maintainers and collaborators for their help to improve and test Chart.js (@nagix, @kurkle, @benmccann, @etimberg and @simonbrunel).

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.

---

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 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)