CVE-2020-1511
Connected User Experiences and Telemetry Service Elevation of Privilege Vulnerability
Reported by microsoft · Published August 17, 2020
An elevation of privilege vulnerability exists when Connected User Experiences and Telemetry Service improperly handles file operations. An attacker who successfully exploited this vulnerability could run processes in an elevated context. An attacker could exploit this vulnerability by running a specially crafted application on the victim system. The security update addresses the vulnerability by correcting how the Connected User Experiences and Telemetry Service handles file operations.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| Windows 10 Version 1803 | Microsoft | publication |
| Windows Server 2016 (Server Core installation) | Microsoft | publication |
| Windows Server version 2004 | Microsoft | publication |
| Windows 10 Version 1809 | Microsoft | publication |
| Windows Server, version 1909 (Server Core installation) | Microsoft | publication |
| Windows Server 2019 | Microsoft | publication |
| Windows 10 Version 1709 | Microsoft | publication |
| Windows Server 2019 (Server Core installation) | Microsoft | publication |
| Windows 10 Version 2004 | Microsoft | publication |
| Windows 10 Version 1903 for x64-based Systems | Microsoft | publication |
| Windows 10 Version 1507 | Microsoft | publication |
| Windows 10 Version 1909 | Microsoft | publication |
6 more packages have a fixed version. See every fix in Lookup.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Microsoft | Windows 10 Version 2004 | 10.0.0 |
| Microsoft | Windows Server version 2004 | 10.0.0 |
| Microsoft | Windows 10 Version 1803 | 10.0.0 |
| Microsoft | Windows 10 Version 1809 | 10.0.0 |
| Microsoft | Windows Server 2019 | 10.0.0 |
| Microsoft | Windows Server 2019 (Server Core installation) | 10.0.0 |
| Microsoft | Windows 10 Version 1909 | 10.0.0 |
| Microsoft | Windows Server, version 1909 (Server Core installation) | 10.0.0 |
| Microsoft | Windows 10 Version 1709 for 32-bit Systems | 10.0.0 |
| Microsoft | Windows 10 Version 1709 | 10.0.0 |
| Microsoft | Windows 10 Version 1903 for 32-bit Systems | 10.0.0 |
| Microsoft | Windows 10 Version 1903 for x64-based Systems | 10.0.0 |
| Microsoft | Windows 10 Version 1903 for ARM64-based Systems | 10.0.0 |
| Microsoft | Windows Server, version 1903 (Server Core installation) | 10.0.0 |
| Microsoft | Windows 10 Version 1507 | 10.0.0 |
| Microsoft | Windows 10 Version 1607 | 10.0.0 |
| Microsoft | Windows Server 2016 | 10.0.0 |
| Microsoft | Windows Server 2016 (Server Core installation) | 10.0.0 |
| Microsoft | Windows 10 Version 1803 | 10.0.0 |
| Microsoft | Windows Server 2016 (Server Core installation) | 10.0.0 |
…and 16 more
Timeline
- Aug 12, 2020 CVE Published
- Apr 14, 2021 EPSS Score (30 in total, the first dated here)
- Feb 23, 2026 CVE Updated
- Mar 10, 2026 Security Advisory (3 in total, the first dated here)
- Sep 4, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2020-1511
vulnetix vdb fixes CVE-2020-1511Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2020-1511/fixes/registry"The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart