CVE-2020-0810 [High] | Security Vulnerability in Visual Studio 2015

An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector or the Visual Studio Standard Collector allows file creation in arbitrary locations.To exploit the vulnerability, an attacker would first have to log on to the system.An attacker could then run a specially crafted application that could exploit the vulnerability and take control of an affected system.The update addresses the vulnerability by not permitting Diagnostics Hub Standard Collector or the Visual Studio Standard Collector to create files in arbitrary locations., aka 'Diagnostic Hub Standard Collector Elevation of Privilege Vulnerability'.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.40%	0.98%	+0.58%
2	2025-11-21	0.28%	0.40%	+0.11%
3	2025-11-18	—	0.28%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.40%

0.98%

+0.58%

2025-11-21

0.28%

0.40%

+0.11%

2025-11-18

—

0.28%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.9	[email protected]
7.2	2.0	HIGH	`AV:L/AC:L/Au:N/C:C/I:C/A:C` Click to expand Access vector (AV:L) Requires local access to the target system. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:N) No authentication is required. Confidentiality impact (C:C) Complete confidentiality impact. Integrity impact (I:C) Complete integrity impact. Availability impact (A:C) Complete availability impact.	3.9	10.0	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.9

[email protected]

7.2

2.0

HIGH

AV:L/AC:L/Au:N/C:C/I:C/A:C Click to expand

Access vector (AV:L): Requires local access to the target system.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:C): Complete confidentiality impact.
Integrity impact (I:C): Complete integrity impact.
Availability impact (A:C): Complete availability impact.

3.9

10.0

[email protected]

Affected software / configurations for CVE-2020-0810

Vendor	Product	Version	Raw CPE
microsoft	visual_studio_2015	—	cpe:2.3:a:microsoft:visual_studio_2015:-:update3::::::
microsoft	visual_studio_2017	>= 15.1, <= 15.9	cpe:2.3:a:microsoft:visual_studio_2017::::::::
microsoft	visual_studio_2019	>= 16.0, <= 16.4	cpe:2.3:a:microsoft:visual_studio_2019::::::::
microsoft	windows_10	—	cpe:2.3:o:microsoft:windows_10:-:::::::*
microsoft	windows_10	1607	cpe:2.3:o:microsoft:windows_10:1607:::::::*
microsoft	windows_10	1709	cpe:2.3:o:microsoft:windows_10:1709:::::::*
microsoft	windows_10	1803	cpe:2.3:o:microsoft:windows_10:1803:::::::*
microsoft	windows_10	1809	cpe:2.3:o:microsoft:windows_10:1809:::::::*
microsoft	windows_10	1903	cpe:2.3:o:microsoft:windows_10:1903:::::::*
microsoft	windows_10	1909	cpe:2.3:o:microsoft:windows_10:1909:::::::*
microsoft	windows_server_2016	—	cpe:2.3:o:microsoft:windows_server_2016:-:::::::*
microsoft	windows_server_2016	1803	cpe:2.3:o:microsoft:windows_server_2016:1803:::::::*
microsoft	windows_server_2016	1903	cpe:2.3:o:microsoft:windows_server_2016:1903:::::::*
microsoft	windows_server_2016	1909	cpe:2.3:o:microsoft:windows_server_2016:1909:::::::*
microsoft	windows_server_2019	—	cpe:2.3:o:microsoft:windows_server_2019:-:::::::*

References for CVE-2020-0810

URL	Tags
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0810	Patch Vendor Advisory

URL

CVE-2020-0810

Exploit prediction scoring system (EPSS) score for CVE-2020-0810

Common vulnerability scoring system (CVSS) metrics for CVE-2020-0810

Weakness enumeration for CVE-2020-0810

Affected software / configurations for CVE-2020-0810

References for CVE-2020-0810