{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2017-4941 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-4941 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-4941 is a high-severity memory corruption vulnerability in Vmware Esxi, published on 20 Dec 2017. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-4941 and fix it if it is affected.\n\nWhat it is: CVE-2017-4941 is a high-severity memory corruption vulnerability in Vmware Esxi, published on 20 Dec 2017. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-4941 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-2017-4941/ (Markdown: https://insights.sbomify.com/CVE-2017-4941/index.md)","id":"CVE-2017-4941","markdown":"https://insights.sbomify.com/CVE-2017-4941/index.md","name":"CVE-2017-4941","record":{"aliases":["GHSA-9hmp-hj7f-46vm"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"VMware virtualization software","requires_auth":"low_privilege","summary":"An authenticated VNC user can trigger a stack overflow to execute arbitrary code in a virtual machine, requiring VNC to be manually enabled and firewall rules adjusted.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[{"product":"esxi","vendor":"vmware"},{"product":"fusion","vendor":"vmware"},{"product":"workstation","vendor":"vmware"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"VMware ESXi (6.0 before ESXi600-201711101-SG, 5.5 ESXi550-201709101-SG), Workstation (12.x before 12.5.8), and Fusion (8.x before 8.5.9) contain a vulnerability that could allow an authenticated VNC session to cause a stack overflow via a specific set of VNC packets. Successful exploitation of this issue could result in remote code execution in a virtual machine via the authenticated VNC session. Note: In order for exploitation to be possible in ESXi, VNC must be manually enabled in a virtual machine's .vmx configuration file. In addition, ESXi must be configured to allow VNC traffic through the built-in firewall.","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":"Memory corruption in ESXi","id":"CVE-2017-4941","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"vmware:esxi","products":["vmware:esxi","vmware:fusion","vmware:workstation"],"type":"memory_corruption","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in Airwatch Console","id":"CVE-2017-4942"},"packages":[],"prev":{"headline":"Cross-site scripting in ESXi","id":"CVE-2017-4940"},"products":["ESXi","Fusion","Workstation"],"published":"2017-12-20","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-09-16","vendors":["VMware"]},"summary":"An authenticated VNC user can trigger a stack overflow to execute arbitrary code in a virtual machine, requiring VNC to be manually enabled and firewall rules adjusted.","url":"https://insights.sbomify.com/CVE-2017-4941/"}