CVE-2019-5531 Vulnerability Analysis & Exploit Details

CVE-2019-5531
Vulnerability Scoring

5.4
/10
Significant Risk

Security assessments indicate that CVE-2019-5531 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2019-5531 Details

Status: Modified

Last updated: 🕟 21 Nov 2024, 04:45 UTC
Originally published on: 🕙 18 Sep 2019, 22:15 UTC

Time between publication and last update: 1890 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

CVE-2019-5531 Vulnerability Summary

CVE-2019-5531: VMware vSphere ESXi (6.7 prior to ESXi670-201810101-SG, 6.5 prior to ESXi650-201811102-SG, and 6.0 prior to ESXi600-201807103-SG) and VMware vCenter Server (6.7 prior to 6.7 U1b, 6.5 prior to 6.5 U2b, and 6.0 prior to 6.0 U3j) contain an information disclosure vulnerability in clients arising from insufficient session expiration. An attacker with physical access or an ability to mimic a websocket connection to a user’s browser may be able to obtain control of a VM Console after the user has logged out or their session has timed out.

Assessing the Risk of CVE-2019-5531

Access Complexity Graph

The exploitability of CVE-2019-5531 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2019-5531

With low attack complexity and no required privileges, CVE-2019-5531 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2019-5531, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2019-5531, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2019-5531 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: Low
    Exploiting CVE-2019-5531 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2019-5531 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.078% (probability of exploit)

EPSS Percentile: 36.9% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 63.1% of others.

CVE-2019-5531 References

External References

CWE Common Weakness Enumeration

CWE-613

Vulnerable Configurations

  • cpe:2.3:o:vmware:esxi:6.7:670-201811001:*:*:*:*:*:*
    cpe:2.3:o:vmware:esxi:6.7:670-201811001:*:*:*:*:*:*
  • cpe:2.3:o:vmware:vsphere_esxi:6.7:*:*:*:*:*:*:*
    cpe:2.3:o:vmware:vsphere_esxi:6.7:*:*:*:*:*:*:*
  • cpe:2.3:o:vmware:vsphere_esxi:6.7:update_1:*:*:*:*:*:*
    cpe:2.3:o:vmware:vsphere_esxi:6.7:update_1:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vsphere_esxi:6.5:a:*:*:*:*:*:*
    cpe:2.3:a:vmware:vsphere_esxi:6.5:a:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vsphere_esxi:6.5:u2:*:*:*:*:*:*
    cpe:2.3:a:vmware:vsphere_esxi:6.5:u2:*:*:*:*:*:*
  • cpe:2.3:o:vmware:vsphere_esxi:6.5:*:*:*:*:*:*:*
    cpe:2.3:o:vmware:vsphere_esxi:6.5:*:*:*:*:*:*:*
  • cpe:2.3:o:vmware:vsphere_esxi:6.5:650-201810002:*:*:*:*:*:*
    cpe:2.3:o:vmware:vsphere_esxi:6.5:650-201810002:*:*:*:*:*:*
  • cpe:2.3:o:vmware:vsphere_esxi:6.5:650-201811001:*:*:*:*:*:*
    cpe:2.3:o:vmware:vsphere_esxi:6.5:650-201811001:*:*:*:*:*:*
  • cpe:2.3:o:vmware:vsphere_esxi:6.5:650-201811002:*:*:*:*:*:*
    cpe:2.3:o:vmware:vsphere_esxi:6.5:650-201811002:*:*:*:*:*:*
  • cpe:2.3:o:vmware:vsphere_esxi:6.5:650-201901001:*:*:*:*:*:*
    cpe:2.3:o:vmware:vsphere_esxi:6.5:650-201901001:*:*:*:*:*:*
  • cpe:2.3:o:vmware:vsphere_esxi:6.5:650-201903001:*:*:*:*:*:*
    cpe:2.3:o:vmware:vsphere_esxi:6.5:650-201903001:*:*:*:*:*:*
  • cpe:2.3:o:vmware:vsphere_esxi:6.5:650-201905001:*:*:*:*:*:*
    cpe:2.3:o:vmware:vsphere_esxi:6.5:650-201905001:*:*:*:*:*:*
  • cpe:2.3:o:vmware:vsphere_esxi:6.5:update_1:*:*:*:*:*:*
    cpe:2.3:o:vmware:vsphere_esxi:6.5:update_1:*:*:*:*:*:*
  • cpe:2.3:o:vmware:vsphere_esxi:6.0:*:*:*:*:*:*:*
    cpe:2.3:o:vmware:vsphere_esxi:6.0:*:*:*:*:*:*:*
  • cpe:2.3:o:vmware:vsphere_esxi:6.0:600-201810001:*:*:*:*:*:*
    cpe:2.3:o:vmware:vsphere_esxi:6.0:600-201810001:*:*:*:*:*:*
  • cpe:2.3:o:vmware:vsphere_esxi:6.0:600-201811001:*:*:*:*:*:*
    cpe:2.3:o:vmware:vsphere_esxi:6.0:600-201811001:*:*:*:*:*:*
  • cpe:2.3:o:vmware:vsphere_esxi:6.0:600-201903001:*:*:*:*:*:*
    cpe:2.3:o:vmware:vsphere_esxi:6.0:600-201903001:*:*:*:*:*:*
  • cpe:2.3:o:vmware:vsphere_esxi:6.0:600-201905001:*:*:*:*:*:*
    cpe:2.3:o:vmware:vsphere_esxi:6.0:600-201905001:*:*:*:*:*:*
  • cpe:2.3:o:vmware:vsphere_esxi:6.0:beta:*:*:*:*:*:*
    cpe:2.3:o:vmware:vsphere_esxi:6.0:beta:*:*:*:*:*:*
  • cpe:2.3:o:vmware:vsphere_esxi:6.0:u1a:*:*:*:*:*:*
    cpe:2.3:o:vmware:vsphere_esxi:6.0:u1a:*:*:*:*:*:*
  • cpe:2.3:o:vmware:vsphere_esxi:6.0:u1b:*:*:*:*:*:*
    cpe:2.3:o:vmware:vsphere_esxi:6.0:u1b:*:*:*:*:*:*
  • cpe:2.3:o:vmware:vsphere_esxi:6.0:u3a:*:*:*:*:*:*
    cpe:2.3:o:vmware:vsphere_esxi:6.0:u3a:*:*:*:*:*:*
  • cpe:2.3:o:vmware:vsphere_esxi:6.0:update_2:*:*:*:*:*:*
    cpe:2.3:o:vmware:vsphere_esxi:6.0:update_2:*:*:*:*:*:*
  • cpe:2.3:o:vmware:vsphere_esxi:6.0:update_3:*:*:*:*:*:*
    cpe:2.3:o:vmware:vsphere_esxi:6.0:update_3:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.0:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.0:a:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.0:a:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.0:b:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.0:b:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.0:u1:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.0:u1:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.0:u1b:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.0:u1b:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.0:u3:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.0:u3:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.0:update2:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.0:update2:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.0:update2a:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.0:update2a:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.0:update2m:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.0:update2m:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.0:update3a:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.0:update3a:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.0:update3b:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.0:update3b:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.0:update3c:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.0:update3c:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.0:update3d:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.0:update3d:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.0:update3e:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.0:update3e:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.0:update3f:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.0:update3f:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.0:update3g:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.0:update3g:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.0:update3h:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.0:update3h:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.0:update3i:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.0:update3i:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.7:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.7:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.7:a:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.7:a:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.7:b:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.7:b:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.7:c:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.7:c:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.7:d:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.7:d:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.7:update1:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.7:update1:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.7:update1b:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.7:update1b:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.7:update2:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.7:update2:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.7:update2a:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.7:update2a:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.7:update2c:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.7:update2c:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.5:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.5:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.5:a:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.5:a:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.5:b:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.5:b:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.5:c:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.5:c:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.5:d:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.5:d:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.5:update1:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.5:update1:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.5:update1b:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.5:update1b:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.5:update1c:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.5:update1c:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.5:update1d:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.5:update1d:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.5:update1e:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.5:update1e:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.5:update1g:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.5:update1g:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.5:update2:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.5:update2:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.5:update2b:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.5:update2b:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.5:update2c:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.5:update2c:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.5:update2d:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.5:update2d:*:*:*:*:*:*
  • cpe:2.3:a:vmware:vcenter_server:6.5:update2g:*:*:*:*:*:*
    cpe:2.3:a:vmware:vcenter_server:6.5:update2g:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2019-5531: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-3797 – A vulnerability classified as critical was found in SeaCMS up to 13.3. This vulnerability affects unknown code of the file /admin_topic.php?action=...
  • CVE-2025-3809 – The Debug Log Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the auto-refresh debug log in all versions up to, and i...
  • CVE-2025-2111 – The Insert Headers And Footers plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.1.1. This i...
  • CVE-2024-13926 – The WP-Syntax WordPress plugin through 1.2 does not properly handle input, allowing an attacker to create a post containing a large number of tags,...
  • CVE-2025-3103 – The CLEVER - HTML5 Radio Player With History - Shoutcast and Icecast - Elementor Widget Addon plugin for WordPress is vulnerable to arbitrary file ...