VMware vCenter Server up to 6.0 U2/6.5 U2/6.7 U2 Log Credentials insufficiently protected credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in VMware vCenter Server up to 6.0 U2/6.5 U2/6.7 U2. Affected is an unknown function of the component Log Handler. Performing a manipulation results in insufficiently protected credentials (Credentials). This vulnerability is reported as CVE-2019-5532. The attack is possible to be carried out remotely. No exploit exists. To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability, which was classified as problematic, was found in VMware vCenter Server up to 6.0 U2/6.5 U2/6.7 U2 (Server Management Software). This affects some unknown processing of the component Log Handler. The manipulation with an unknown input leads to a insufficiently protected credentials vulnerability (Credentials). CWE is classifying the issue as CWE-522. The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. This is going to have an impact on confidentiality. The summary by CVE is:
VMware vCenter Server (6.7.x prior to 6.7 U3, 6.5 prior to 6.5 U3 and 6.0 prior to 6.0 U3j) contains an information disclosure vulnerability due to the logging of credentials in plain-text for virtual machines deployed through OVF. A malicious user with access to the log files containing vCenter OVF-properties of a virtual machine deployed from an OVF may be able to view the credentials used to deploy the OVF (typically the root account of the virtual machine).
The weakness was disclosed 09/18/2019 (Website). It is possible to read the advisory at vmware.com. This vulnerability is uniquely identified as CVE-2019-5532 since 01/07/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. Required for exploitation is a authentication. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1552 according to MITRE ATT&CK.
Applying the patch 6.0 U3j/6.5 U3/6.7 U3 is able to eliminate this problem.
The entries VDB-141986 and VDB-141988 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.vmware.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.2
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.7
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: Insufficiently protected credentials / Credentials
CWE: CWE-522
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 6.0 U3j/6.5 U3/6.7 U3
Timeline
01/07/2019 🔍09/18/2019 🔍
09/19/2019 🔍
12/26/2023 🔍
Sources
Vendor: vmware.comAdvisory: 154536
Status: Not defined
Confirmation: 🔍
CVE: CVE-2019-5532 (🔍)
GCVE (CVE): GCVE-0-2019-5532
GCVE (VulDB): GCVE-100-141987
scip Labs: https://www.scip.ch/en/?labs.20060413
See also: 🔍
Entry
Created: 09/19/2019 14:33Updated: 12/26/2023 13:29
Changes: 09/19/2019 14:33 (59), 08/30/2020 14:47 (1), 12/26/2023 13:29 (4)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.