G Data Security Guardium Big Data Intelligence 3.1 Credentials credentials management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in G Data Security Guardium Big Data Intelligence 3.1. This affects an unknown function. Executing a manipulation can lead to credentials management (Credentials). This vulnerability is handled as CVE-2018-1377. It is possible to launch the attack on the local host. There is not any exploit available.
Details
A vulnerability has been found in G Data Security Guardium Big Data Intelligence 3.1 (Big Data Software) and classified as problematic. This vulnerability affects some unknown functionality. The manipulation with an unknown input leads to a credentials management vulnerability (Credentials). The CWE definition for the vulnerability is CWE-255. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
IBM Security Guardium Big Data Intelligence (SonarG) 3.1 stores user credentials in plain in clear text which can be read by a local user. IBM X-Force ID: 137778.
The bug was discovered 02/21/2018. The weakness was released 02/26/2018 by ryan (Website). The advisory is shared for download at ibm.com. This vulnerability was named CVE-2018-1377 since 12/13/2017. The attack needs to be approached locally. A single 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 T1552.
The vulnerability was handled as a non-public zero-day exploit for at least 5 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 103213†). Entry connected to this vulnerability is available at VDB-113832. Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
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: 🔍
NVD Base Score: 🔍
Exploiting
Name: CredentialsClass: Credentials management / Credentials
CWE: CWE-255
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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/13/2017 🔍02/21/2018 🔍
02/21/2018 🔍
02/26/2018 🔍
02/26/2018 🔍
02/27/2018 🔍
02/10/2023 🔍
Sources
Advisory: ibm.comResearcher: ryan
Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-1377 (🔍)
GCVE (CVE): GCVE-0-2018-1377
GCVE (VulDB): GCVE-100-113836
X-Force: 137778
SecurityFocus: 103213 - IBM Security Guardium Big Data Intelligence CVE-2018-1377 Local Information Disclosure Vulnerability
See also: 🔍
Entry
Created: 02/27/2018 07:44Updated: 02/10/2023 11:35
Changes: 02/27/2018 07:44 (61), 01/08/2020 16:35 (5), 02/10/2023 11:35 (3)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.