CVE-2018-0952 json
An Elevation of Privilege vulnerability exists when Diagnostics Hub Standard Collector allows file creation in arbitrary locations, aka "Di…
published 8y ago modified 4mo ago also EUVD-2018-1732
- cvss
- 7.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.2%
- EPSS 6.2% chance of exploitation in 30 days, percentile 93%
- public exploits
- 1
- Exploit-DB
Summary
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.
Patch / fix
Is CVE-2018-0952 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-45244)
Exploit prediction
6.23% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-45244 Microsoft Windows 10 - Diagnostics Hub Standard Collector Service Privilege Escalation local, 2018-08-22
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.8 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Affected products
- Microsoft Windows Server 2016
- Microsoft Windows 10
- Microsoft Microsoft Visual Studio
- Microsoft Windows 10 Servers
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2018-0952
patch, vendor-advisory
-
exploit-db.com
/exploits/45244/
exploit, third-party-advisory, vdb-entry
-
securityfocus.com
/bid/105048
vdb-entry, third-party-advisory
-
securitytracker.com
/id/1041466
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-0952
- NVD CVE-2018-0952
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.