IBM Security Guardium 11.1 Account Lockout excessive authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in IBM Security Guardium 11.1. It has been classified as problematic. Affected is an unknown function of the component Account Lockout. This manipulation causes excessive authentication. This vulnerability appears as CVE-2020-4193. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability classified as problematic was found in IBM Security Guardium 11.1 (Policy Management Software). Affected by this vulnerability is an unknown code block of the component Account Lockout. The manipulation with an unknown input leads to a excessive authentication vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality. The summary by CVE is:
IBM Security Guardium 11.1 uses an inadequate account lockout setting that could allow a remote attacker to brute force account credentials. IBM X-Force ID: 174857.
The weakness was presented 06/04/2020 (Website). The advisory is shared at exchange.xforce.ibmcloud.com. This vulnerability is known as CVE-2020-4193 since 12/30/2019. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/05/2020). It is expected to see the exploit prices for this product increasing in the near future.MITRE ATT&CK project uses the attack technique T1110.001 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-156132 and VDB-156131 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.ibm.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.1VulDB Meta Temp Score: 4.1
VulDB Base Score: 3.7
VulDB Temp Score: 3.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.4
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/30/2019 🔍06/04/2020 🔍
06/05/2020 🔍
10/22/2020 🔍
Sources
Vendor: ibm.comAdvisory: exchange.xforce.ibmcloud.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2020-4193 (🔍)
GCVE (CVE): GCVE-0-2020-4193
GCVE (VulDB): GCVE-100-156133
X-Force: 174857
See also: 🔍
Entry
Created: 06/05/2020 10:09Updated: 10/22/2020 09:17
Changes: 06/05/2020 10:09 (41), 06/05/2020 10:14 (12), 10/22/2020 09:10 (1), 10/22/2020 09:17 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.