chore(deps): update dependency bcrypt to v3.1.22 [security]#1247
Open
renovate[bot] wants to merge 1 commit intostagingfrom
Open
chore(deps): update dependency bcrypt to v3.1.22 [security]#1247renovate[bot] wants to merge 1 commit intostagingfrom
renovate[bot] wants to merge 1 commit intostagingfrom
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## staging #1247 +/- ##
========================================
Coverage 77.59% 77.59%
========================================
Files 54 54
Lines 1406 1406
========================================
Hits 1091 1091
Misses 315 315 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.1.21→3.1.22GitHub Vulnerability Alerts
CVE-2026-33306
Impact
An integer overflow in the Java BCrypt implementation for JRuby can cause zero iterations in the strengthening loop. Impacted applications must be setting the cost to 31 to see this happen.
The JRuby implementation of bcrypt-ruby (
BCrypt.java) computes the key-strengthening round count as a signed 32-bit integer. Whencost=31(the maximum allowed by the gem), signed integer overflow causes the round count to become negative, and the strengthening loop executes zero iterations. This collapses bcrypt from 2^31 rounds of exponential key-strengthening to effectively constant-time computation — only the initial EksBlowfish key setup and final 64x encryption phase remain.The resulting hash looks valid (
$2a$31$...) and verifies correctly viacheckpw, making the weakness invisible to the application. This issue is triggered only when cost=31 is used or when verifying a$2a$31$hash.Patches
This problem has been fixed in version 3.1.22
Workarounds
Set the cost to something less than 31.
Configuration
📅 Schedule: Branch creation - "" in timezone Europe/Amsterdam, 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.
This PR was generated by Mend Renovate. View the repository job log.