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

fix(deps): update dependency bcrypt to v5 [security] #316

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 20, 2020

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
bcrypt 3.0.8 -> 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 (bcrypt)

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

v4.0.1

Compare Source

  • Fix compilation errors in Alpine linux

v4.0.0

Compare Source

  • Switch to NAPI bcrypt
    • Drop support for NodeJS 8

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 becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/npm-bcrypt-vulnerability branch 30 times, most recently from 8d88e75 to 2f417d5 Compare October 30, 2020 19:55
@renovate renovate bot force-pushed the renovate/npm-bcrypt-vulnerability branch 17 times, most recently from 23594f9 to 56359c1 Compare November 5, 2020 21:25
@renovate renovate bot force-pushed the renovate/npm-bcrypt-vulnerability branch from 56359c1 to aa26709 Compare August 14, 2021 19:04
@renovate renovate bot force-pushed the renovate/npm-bcrypt-vulnerability branch from aa26709 to 7cc5298 Compare January 5, 2022 05:43
@renovate renovate bot changed the title fix(deps): update dependency bcrypt to v5 [security] fix(deps): update dependency bcrypt to v5 [SECURITY] Jun 27, 2022
@renovate renovate bot changed the title fix(deps): update dependency bcrypt to v5 [SECURITY] fix(deps): update dependency bcrypt to v5 [security] Jun 28, 2022
@renovate renovate bot force-pushed the renovate/npm-bcrypt-vulnerability branch from 7cc5298 to 29e4baa Compare December 15, 2022 21:48
@renovate renovate bot force-pushed the renovate/npm-bcrypt-vulnerability branch 4 times, most recently from d3b420a to 67bad65 Compare January 14, 2023 14:25
@renovate renovate bot force-pushed the renovate/npm-bcrypt-vulnerability branch from 67bad65 to 82c430e Compare July 9, 2023 01:47
@ghelton
Copy link

ghelton commented Jul 12, 2023

I spent a number of hours trying to get this to run on my M1 mac and I think bcrypt might have been the culprit. I believe this should be merged in save others the headache.

If anyone else it getting an error like this, you should try installing the latest bcrypt via yarn:
/Users/ghelton/git/web-security-fundamentals/node_modules/bcrypt: Command failed.

@renovate renovate bot force-pushed the renovate/npm-bcrypt-vulnerability branch from 82c430e to ba46b74 Compare January 7, 2025 16:30
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.

1 participant