CVE-2019-0574 in the critical feed json
An elevation of privilege vulnerability exists when the Windows Data Sharing Service improperly handles file operations, aka "Windows Data…
published 7y ago modified 4mo ago also EUVD-2019-1341
- cvss
- 7.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 19.4%
- EPSS 19.4% chance of exploitation in 30 days, percentile 97%
- public exploits
- 1
- Exploit-DB
Summary
An elevation of privilege vulnerability exists when the Windows Data Sharing Service improperly handles file operations, aka "Windows Data Sharing Service Elevation of Privilege Vulnerability." This affects Windows Server 2016, Windows 10, Windows Server 2019, Windows 10 Servers. This CVE ID is unique from CVE-2019-0571, CVE-2019-0572, CVE-2019-0573.
Patch / fix
Is CVE-2019-0574 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-46160)
Exploit prediction
19.45% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-46160 Microsoft Windows 10 - DSSVC MoveFileInheritSecurity Privilege Escalation local, 2019-01-14
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.8 | CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected products
- Microsoft Windows Server 2016
- Microsoft Windows 10
- Microsoft Windows Server 2019
- Microsoft Windows 10 Servers
Classification
- Weakness
-
- CWE-59 Improper Link Resolution Before File Access
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2019-0574
patch, vendor-advisory
-
exploit-db.com
/exploits/46160/
exploit, third-party-advisory, vdb-entry
-
securityfocus.com
/bid/106431
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2019-0574
- NVD CVE-2019-0574
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.