{"answers":{"affected":"It affects 4 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-0952 exists.","fix":"No fix has been published for CVE-2018-0952 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-0952 is a high-severity vulnerability in Microsoft Visual Studio 2017, published on 15 Aug 2018. 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-2018-0952 and fix it if it is affected.\n\nWhat it is: CVE-2018-0952 is a high-severity vulnerability in Microsoft Visual Studio 2017, published on 15 Aug 2018. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-0952 exists.\n\nAffected product: Microsoft Visual Studio 2017. 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-2018-0952/ (Markdown: https://insights.sbomify.com/CVE-2018-0952/index.md)","id":"CVE-2018-0952","markdown":"https://insights.sbomify.com/CVE-2018-0952/index.md","name":"CVE-2018-0952","record":{"aliases":["GHSA-g92w-m5cw-jw9w"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Windows OS","requires_auth":"low_privilege","summary":"Attackers can exploit Diagnostics Hub Standard Collector to create files in arbitrary locations, leading to privilege escalation on Windows systems.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"visual_studio_2015","vendor":"microsoft"},{"product":"visual_studio_2017","vendor":"microsoft"},{"product":"windows_10","vendor":"microsoft"},{"product":"windows_server_2016","vendor":"microsoft"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"An Elevation of Privilege vulnerability exists when Diagnostics Hub Standard Collector allows file creation in arbitrary locations, aka \"Diagnostic Hub Standard Collector Elevation Of Privilege Vulnerability.\" This affects Windows Server 2016, Windows 10, Microsoft Visual Studio, Windows 10 Servers.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2018-08-21","github_poc":1,"max_poc_stars":110,"metasploit":0,"nuclei":0,"refs":[{"date":"2018-08-21T20:29:10Z","kind":"github_poc","ref":"https://github.com/atredispartners/CVE-2018-0952-SystemCollector","stars":110,"title":"PoC for Privilege Escalation in Windows 10 Diagnostics Hub Standard Collector Service"},{"date":"2018-08-22","kind":"exploitdb","ref":"45244","stars":null,"title":"Microsoft Windows 10 - Diagnostics Hub Standard Collector Service Privilege Escalation"}],"tier":"weaponised"},"has_fix":null,"headline":"Privilege escalation in Microsoft Visual Studio","id":"CVE-2018-0952","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:visual_studio_2017","products":["microsoft:visual_studio_2017","microsoft:windows_10","microsoft:windows_server_2016"],"type":"privilege_escalation","year":"2018"},"n_packages":0,"n_references":4,"next":{"headline":"Memory corruption in ChakraCore","id":"CVE-2018-0953"},"packages":[],"prev":{"headline":"Memory corruption in Microsoft Edge","id":"CVE-2018-0951"},"products":["Microsoft Visual Studio","Windows 10","Windows 10 Servers","Windows Server 2016"],"published":"2018-08-15","related":[{"cvss_score":7.8,"headline":"Privilege escalation in Microsoft Visual Studio","id":"CVE-2020-0793","kev_date_added":null,"published":"2020-03-12"},{"cvss_score":7.8,"headline":"Privilege escalation in Microsoft Visual Studio","id":"CVE-2020-0810","kev_date_added":null,"published":"2020-03-12"},{"cvss_score":5.5,"headline":"Privilege escalation in Microsoft Visual Studio","id":"CVE-2020-0900","kev_date_added":null,"published":"2020-04-15"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["Microsoft"]},"summary":"Attackers can exploit Diagnostics Hub Standard Collector to create files in arbitrary locations, leading to privilege escalation on Windows systems.","url":"https://insights.sbomify.com/CVE-2018-0952/"}