Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
💎
💎 RubyGems
Not in CISA KEV
HIGH severity

GHSA-jc8m-cxhj-668x

HIGHFix: Sorcery/sorcery#235

GHSA-jc8m-cxhj-668x is a high-severity (CVSS 8.3) CWE-307 vulnerability in sorcery. O3 Security confirms whether GHSA-jc8m-cxhj-668x is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Improper Restriction of Excessive Authentication Attempts in Sorcery

Also known asCVE-2020-11052
Published
May 7, 2020
Updated
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Jul 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
💎sorcery

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Brute force vulnerability when using password authentication via Sorcery. The brute force protection submodule will prevent a brute force attack for the defined lockout period, but once expired protection will not be re-enabled until a user or malicious actor logs in successfully. This does not affect users that do not use the built-in brute force protection submodule, nor users that use permanent account lockout.

Patches

Patched as of version 0.15.0.

Workarounds

Currently no workarounds, other than monkey patching the authenticate method provided by Sorcery or upgrading to version 0.15.0.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
💎RubyGemssorceryall versions0.15.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sorcery. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update sorcery to 0.15.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jc8m-cxhj-668x is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-jc8m-cxhj-668x is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-jc8m-cxhj-668x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Brute force vulnerability when using password authentication via Sorcery. The brute force protection submodule will prevent a brute force attack for the defined lockout period, but once expired protection will not be re-enabled until a user or malicious actor logs in successfully. This does not affect users that do not use the built-in brute force protection submodule, nor users that use permanent account lockout. ### Patches Patched as of version `0.15.0`. ### Workarounds Currently no workarounds, other than monkey patching the authenticate method provided by Sorcery or upgrading
O3 Security · Impact-Aware SCA

Is GHSA-jc8m-cxhj-668x in your dependencies?

O3 detects GHSA-jc8m-cxhj-668x across RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-jc8m-cxhj-668x: sorcery (High 8.3) | O3 Security