CVE-2019-0552 json
An elevation of privilege exists in Windows COM Desktop Broker, aka "Windows COM Elevation of Privilege Vulnerability." This affects Window…
published 7y ago modified 4mo ago also EUVD-2019-1322
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.5%
- EPSS 2.5% chance of exploitation in 30 days, percentile 85%
- public exploits
- 1
- Exploit-DB
Summary
An elevation of privilege exists in Windows COM Desktop Broker, aka "Windows COM Elevation of Privilege Vulnerability." This affects Windows Server 2012 R2, Windows RT 8.1, Windows Server 2019, Windows Server 2016, Windows 8.1, Windows 10, Windows 10 Servers.
Patch / fix
Is CVE-2019-0552 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-46162)
Exploit prediction
2.54% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-46162 Microsoft Windows 10 - COM Desktop Broker Privilege Escalation local, 2019-01-14
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/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 2019
- Microsoft Windows Server 2016
- Microsoft Windows 8.1
- Microsoft Windows 10
- Microsoft Windows 10 Servers
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2019-0552
patch, vendor-advisory
-
exploit-db.com
/exploits/46162/
exploit, third-party-advisory
-
securityfocus.com
/bid/106407
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2019-0552
- NVD CVE-2019-0552
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.