{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2019-5531 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-5531 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-5531 is a medium-severity vulnerability in Vmware Esxi, published on 18 Sep 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-5531 and fix it if it is affected.\n\nWhat it is: CVE-2019-5531 is a medium-severity vulnerability in Vmware Esxi, published on 18 Sep 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-5531 in the wild and no public exploit code.\n\nAffected product: Vmware Esxi. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-5531/ (Markdown: https://insights.sbomify.com/CVE-2019-5531/index.md)","id":"CVE-2019-5531","markdown":"https://insights.sbomify.com/CVE-2019-5531/index.md","name":"CVE-2019-5531","record":{"aliases":["GHSA-7623-hj89-p4cw"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"VMware vSphere/Center","requires_auth":"none","summary":"Attackers with physical access or websocket mimicry can hijack VM consoles after user logout due to insufficient session expiration in VMware vSphere and vCenter.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[{"product":"esxi","vendor":"vmware"},{"product":"vcenter_server","vendor":"vmware"},{"product":"vsphere_esxi","vendor":"vmware"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in VMware vCenter Server","id":"CVE-2019-5531","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"vmware:esxi","products":["vmware:esxi","vmware:vcenter_server"],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in vCenter Server","id":"CVE-2019-5532"},"packages":[],"prev":{"headline":"Security feature bypass in InstallBuilder","id":"CVE-2019-5530"},"products":["VMware vCenter Server","VMware vSphere ESXi"],"published":"2019-09-18","related":[{"cvss_score":2.7,"headline":"Broadcom VMWare ESX Insufficient Logging","id":"CVE-2026-41709","kev_date_added":"2026-10-28","published":"2026-07-30"},{"cvss_score":9.6,"headline":"Information disclosure in VMware ESXi","id":"CVE-2019-5521","kev_date_added":null,"published":"2019-09-20"},{"cvss_score":9.3,"headline":"Use-after-free vulnerability","id":"CVE-2024-22252","kev_date_added":null,"published":"2024-03-05"},{"cvss_score":9.3,"headline":"Cross-site scripting in ESXi","id":"CVE-2020-3955","kev_date_added":null,"published":"2020-04-29"},{"cvss_score":9.3,"headline":"Auth bypass in n/a","id":"CVE-2010-4573","kev_date_added":null,"published":"2010-12-22"},{"cvss_score":8.8,"headline":"Use after free in ESXi, Workstation, Fusion, VMRC and Horizon Client","id":"CVE-2019-5527","kev_date_added":null,"published":"2019-10-10"},{"cvss_score":8.8,"headline":"Memory corruption in VMware ESXi, VMware Workstation, and VMware Fusion","id":"CVE-2018-6981","kev_date_added":null,"published":"2018-12-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["VMware"]},"summary":"Attackers with physical access or websocket mimicry can hijack VM consoles after user logout due to insufficient session expiration in VMware vSphere and vCenter.","url":"https://insights.sbomify.com/CVE-2019-5531/"}