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

Update dependency bcrypt to v5 [SECURITY] (master-step12) #1468

Open
wants to merge 1 commit into
base: master-step12
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Aug 21, 2020

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
bcrypt 4.0.1 -> 5.0.0 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2020-7689

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


Release Notes

kelektiv/node.bcrypt.js

v5.0.0

Compare Source

  • 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

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate
Copy link
Author

renovate bot commented Mar 25, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

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.

None yet

1 participant