Sorcery up to 0.14.x Password Authentication excessive authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Sorcery up to 0.14.x. Affected by this vulnerability is an unknown functionality of the component Password Authentication. Such manipulation leads to excessive authentication. This vulnerability is referenced as CVE-2020-11052. It is possible to launch the attack remotely. No exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability was found in Sorcery up to 0.14.x. It has been rated as problematic. Affected by this issue is an unknown code block of the component Password Authentication. The manipulation with an unknown input leads to a excessive authentication vulnerability. Using CWE to declare the problem leads to CWE-307. The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it more susceptible to brute force attacks. Impacted is confidentiality. CVE summarizes:
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.
The weakness was published 05/07/2020 (GitHub Repository). The advisory is shared for download at github.com. This vulnerability is handled as CVE-2020-11052 since 03/30/2020. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1110.001.
Upgrading to version 0.15.0 eliminates this vulnerability.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Name
Version
Website
- Product: https://github.com/Sorcery/sorcery/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.1VulDB Meta Temp Score: 5.9
VulDB Base Score: 4.0
VulDB Temp Score: 3.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.3
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Excessive authenticationCWE: CWE-307 / CWE-799 / CWE-400
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Sorcery 0.15.0
Timeline
03/30/2020 🔍05/07/2020 🔍
05/08/2020 🔍
10/15/2020 🔍
Sources
Product: github.comAdvisory: github.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2020-11052 (🔍)
GCVE (CVE): GCVE-0-2020-11052
GCVE (VulDB): GCVE-100-154880
Entry
Created: 05/08/2020 10:13Updated: 10/15/2020 21:43
Changes: 05/08/2020 10:13 (39), 05/08/2020 10:18 (11), 10/15/2020 21:38 (1), 10/15/2020 21:43 (1)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.