Update dependency bcrypt to v3.1.22 [SECURITY]#877
Update dependency bcrypt to v3.1.22 [SECURITY]#877renovate[bot] wants to merge 1 commit intomainfrom
Conversation
GitLab Pipeline ActionGeneral informationLink to pipeline: https://gitlab.com/code0-tech/development/sagittarius/-/pipelines/2396719732 Status: Passed Job summariesrspec: [ee]Coverage report available at https://code0-tech.gitlab.io/-/development/sagittarius/-/jobs/13570493880/artifacts/tmp/coverage/index.html rspec: [ce]Coverage report available at https://code0-tech.gitlab.io/-/development/sagittarius/-/jobs/13570493877/artifacts/tmp/coverage/index.html rubocop727 files inspected, no offenses detected |
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 - "" (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.
This PR was generated by Mend Renovate. View the repository job log.