{"answers":{"affected":"It affects 5 products.","exploited":"There is no known exploitation of CVE-2018-8599 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-8599 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-8599 is a high-severity vulnerability in Microsoft Visual Studio, published on 12 Dec 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-8599 and fix it if it is affected.\n\nWhat it is: CVE-2018-8599 is a high-severity vulnerability in Microsoft Visual Studio, published on 12 Dec 2018. 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-2018-8599 in the wild and no public exploit code.\n\nAffected product: Microsoft Visual Studio. 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-8599/ (Markdown: https://insights.sbomify.com/CVE-2018-8599/index.md)","id":"CVE-2018-8599","markdown":"https://insights.sbomify.com/CVE-2018-8599/index.md","name":"CVE-2018-8599","record":{"aliases":["GHSA-v453-rppj-85f4"],"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":"An attacker can elevate privileges by exploiting improper file operation impersonation in the Diagnostics Hub Standard Collector Service on Windows systems.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"visual_studio","vendor":"microsoft"},{"product":"visual_studio_2017","vendor":"microsoft"},{"product":"windows_10","vendor":"microsoft"},{"product":"windows_server_2016","vendor":"microsoft"},{"product":"windows_server_2019","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":[{"id":"CWE-273","name":"Improper Check for Dropped Privileges"}],"description":"An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector Service improperly impersonates certain file operations, aka \"Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability.\" This affects Microsoft Visual Studio, Windows Server 2019, Windows Server 2016, Windows 10, Windows 10 Servers.","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":"Privilege escalation in Microsoft Visual Studio","id":"CVE-2018-8599","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:visual_studio","products":["microsoft:visual_studio","microsoft:visual_studio_2017","microsoft:windows_10","microsoft:windows_server_2016","microsoft:windows_server_2019"],"type":"privilege_escalation","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in Azure App","id":"CVE-2018-8600"},"packages":[],"prev":{"headline":"Information disclosure in Microsoft Excel","id":"CVE-2018-8598"},"products":["Microsoft Visual Studio","Windows 10","Windows 10 Servers","Windows Server 2016","Windows Server 2019"],"published":"2018-12-12","related":[{"cvss_score":8.8,"headline":"Visual Studio Elevation of Privilege Vulnerability","id":"CVE-2025-49739","kev_date_added":null,"published":"2025-07-08"},{"cvss_score":8.8,"headline":"Visual Studio Remote Code Execution Vulnerability","id":"CVE-2022-35777","kev_date_added":null,"published":"2022-08-09"},{"cvss_score":8.8,"headline":"Visual Studio Remote Code Execution Vulnerability","id":"CVE-2022-35825","kev_date_added":null,"published":"2022-08-09"},{"cvss_score":8.8,"headline":"Visual Studio Remote Code Execution Vulnerability","id":"CVE-2022-35826","kev_date_added":null,"published":"2022-08-09"},{"cvss_score":8.8,"headline":"Visual Studio Remote Code Execution Vulnerability","id":"CVE-2022-35827","kev_date_added":null,"published":"2022-08-09"},{"cvss_score":7.8,"headline":"Visual Studio Elevation of Privilege Vulnerability","id":"CVE-2024-20656","kev_date_added":null,"published":"2024-01-09"},{"cvss_score":7.8,"headline":"Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability","id":"CVE-2021-28313","kev_date_added":null,"published":"2021-04-13"}],"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":["Microsoft"]},"summary":"An attacker can elevate privileges by exploiting improper file operation impersonation in the Diagnostics Hub Standard Collector Service on Windows systems.","url":"https://insights.sbomify.com/CVE-2018-8599/"}