Описание
Improper Restriction of Excessive Authentication Attempts in Sorcery
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.
Ссылки
- https://github.com/Sorcery/sorcery/security/advisories/GHSA-jc8m-cxhj-668x
- https://nvd.nist.gov/vuln/detail/CVE-2020-11052
- https://github.com/Sorcery/sorcery/issues/231
- https://github.com/Sorcery/sorcery/pull/235
- https://github.com/Sorcery/sorcery/commit/0f116d223826895a73b12492f17486e5d54ab7a7
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/sorcery/CVE-2020-11052.yml
Пакеты
sorcery
< 0.15.0
0.15.0
Связанные уязвимости
In Sorcery before 0.15.0, there is a 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. This has been patched in 0.15.0.