CVE-2019-0570 json
An elevation of privilege vulnerability exists when the Windows Runtime improperly handles objects in memory, aka "Windows Runtime Elevatio…
published 7y ago modified 4mo ago also EUVD-2019-1337
- cvss
- 7.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.0%
- EPSS 3.0% chance of exploitation in 30 days, percentile 87%
- public exploits
- 1
- Exploit-DB
Summary
An elevation of privilege vulnerability exists when the Windows Runtime improperly handles objects in memory, aka "Windows Runtime Elevation of Privilege Vulnerability." This affects Windows Server 2012 R2, Windows RT 8.1, Windows Server 2012, Windows Server 2019, Windows Server 2016, Windows 8.1, Windows 10, Windows 10 Servers.
Patch / fix
Is CVE-2019-0570 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-46184)
Exploit prediction
3.00% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-46184 Microsoft Windows 10 - 'RestrictedErrorInfo' Unmarshal Section Handle Use-After-Free dos, 2019-01-16
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 | 4.6 | AV:L/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- Microsoft Windows Server 2012 R2
- Microsoft Windows RT 8.1
- Microsoft Windows Server 2012
- Microsoft Windows Server 2019
- Microsoft Windows Server 2016
- Microsoft Windows 8.1
- Microsoft Windows 10
- Microsoft Windows 10 Servers
Classification
- Weakness
-
- CWE-416 Use After Free
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2019-0570
patch, vendor-advisory
-
exploit-db.com
/exploits/46184/
exploit, third-party-advisory
-
securityfocus.com
/bid/106415
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2019-0570
- NVD CVE-2019-0570
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.