{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2017-4912 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-4912 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-4912 is a high-severity memory corruption vulnerability in Vmware Workstation, published on 8 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-4912 and fix it if it is affected.\n\nWhat it is: CVE-2017-4912 is a high-severity memory corruption vulnerability in Vmware Workstation, published on 8 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-4912 in the wild and no public exploit code.\n\nAffected product: Vmware Workstation. 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-4912/ (Markdown: https://insights.sbomify.com/CVE-2017-4912/index.md)","id":"CVE-2017-4912","markdown":"https://insights.sbomify.com/CVE-2017-4912/index.md","name":"CVE-2017-4912","record":{"aliases":["GHSA-4cr9-chr7-w4pj"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"VMware Workstation","requires_auth":"low_privilege","summary":"Out-of-bounds read in TTF parser allows guest code execution or DoS on host if virtual printing is enabled.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[{"product":"horizon_view","vendor":"vmware"},{"product":"workstation","vendor":"vmware"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"VMware Workstation (12.x prior to 12.5.3) and Horizon View Client (4.x prior to 4.4.0) contain multiple out-of-bounds read vulnerabilities in TrueType Font (TTF) parser in the TPView.dll. On Workstation, this may allow a guest to execute code or perform a Denial of Service on the Windows OS that runs Workstation. In the case of a Horizon View Client, this may allow a View desktop to execute code or perform a Denial of Service on the Windows OS that runs the Horizon View Client. Exploitation is only possible if virtual printing has been enabled. This feature is not enabled by default on Workstation but it is enabled by default on Horizon View.","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 Horizon View Client for Windows","id":"CVE-2017-4912","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"vmware:workstation","products":["vmware:workstation"],"type":"memory_corruption","year":"2017"},"n_packages":0,"n_references":4,"next":{"headline":"Integer overflow in Horizon View Client for Windows","id":"CVE-2017-4913"},"packages":[],"prev":{"headline":"Memory corruption in Horizon View Client for Windows","id":"CVE-2017-4911"},"products":["Horizon View Client for Windows","Workstation"],"published":"2017-06-08","related":[{"cvss_score":9.8,"headline":"Memory corruption in Horizon View","id":"CVE-2017-4907","kev_date_added":null,"published":"2017-06-08"},{"cvss_score":9.8,"headline":"Command injection in Horizon View Client for Mac","id":"CVE-2017-4918","kev_date_added":null,"published":"2017-06-08"},{"cvss_score":7.8,"headline":"Memory corruption in Horizon View Client for Windows","id":"CVE-2017-4935","kev_date_added":null,"published":"2017-11-17"},{"cvss_score":7.8,"headline":"Memory corruption in Horizon View Client for Windows","id":"CVE-2017-4936","kev_date_added":null,"published":"2017-11-17"},{"cvss_score":7.8,"headline":"Memory corruption in Horizon View Client for Windows","id":"CVE-2017-4937","kev_date_added":null,"published":"2017-11-17"},{"cvss_score":7.8,"headline":"Memory corruption in Horizon View Client for Windows","id":"CVE-2017-4908","kev_date_added":null,"published":"2017-06-08"},{"cvss_score":7.8,"headline":"Memory corruption in Horizon View Client for Windows","id":"CVE-2017-4909","kev_date_added":null,"published":"2017-06-08"}],"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-05","vendors":["VMware"]},"summary":"Out-of-bounds read in TTF parser allows guest code execution or DoS on host if virtual printing is enabled.","url":"https://insights.sbomify.com/CVE-2017-4912/"}