Lenovo XClarity Administrator up to 2.3.x Log File Credentials log file
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Lenovo XClarity Administrator up to 2.3.x. It has been classified as problematic. Affected by this issue is some unknown functionality of the component Log File Handler. This manipulation causes log file (Credentials). This vulnerability is tracked as CVE-2019-6158. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in Lenovo XClarity Administrator up to 2.3.x. It has been declared as problematic. Affected by this vulnerability is an unknown code block of the component Log File Handler. The manipulation with an unknown input leads to a log file vulnerability (Credentials). The CWE definition for the vulnerability is CWE-532. Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information. As an impact it is known to affect confidentiality. The summary by CVE is:
An internal product security audit of Lenovo XClarity Administrator (LXCA) discovered HTTP proxy credentials being written to a log file in clear text. This only affects LXCA when HTTP proxy credentials have been configured. This affects LXCA versions 2.0.0 to 2.3.x.
The bug was discovered 05/02/2019. The weakness was disclosed 05/03/2019 (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2019-6158 since 01/11/2019. The attack can be launched remotely. The requirement for exploitation is a single authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 1 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.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.lenovo.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.9
NVD Vector: 🔍
CNA Base Score: 8.7
CNA Vector (Lenovo Group Ltd.): 🔍
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: Log file / Credentials
CWE: CWE-532 / CWE-200 / CWE-284
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
01/11/2019 🔍05/02/2019 🔍
05/03/2019 🔍
05/04/2019 🔍
09/12/2023 🔍
Sources
Vendor: lenovo.comAdvisory: securityfocus.com⛔
Status: Not defined
CVE: CVE-2019-6158 (🔍)
GCVE (CVE): GCVE-0-2019-6158
GCVE (VulDB): GCVE-100-134377
SecurityFocus: 108165
Entry
Created: 05/04/2019 08:29Updated: 09/12/2023 13:20
Changes: 05/04/2019 08:29 (55), 06/06/2020 17:15 (2), 09/12/2023 13:14 (3), 09/12/2023 13:20 (12)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.