Skip to content

Improper Restriction of Excessive Authentication Attempts in Sorcery

High severity GitHub Reviewed Published May 2, 2020 in Sorcery/sorcery • Updated May 16, 2023

Package

bundler sorcery (RubyGems)

Affected versions

< 0.15.0

Patched versions

0.15.0

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.

References

@joshbuker joshbuker published to Sorcery/sorcery May 2, 2020
Reviewed May 7, 2020
Published to the GitHub Advisory Database May 7, 2020
Last updated May 16, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

EPSS score

0.271%
(69th percentile)

Weaknesses

CVE ID

CVE-2020-11052

GHSA ID

GHSA-jc8m-cxhj-668x

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.