The UNC implementation in Microsoft Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, and Windows RT Gold and 8.1 does not include authentication from the server to the client, which allows remote attackers to execute arbitrary code by making crafted data available on a UNC share, as demonstrated by Group Policy data from a spoofed domain controller, aka Group Policy Remote Code Execution Vulnerability.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Windows_7 | Microsoft | –sp1 (including) | –sp1 (including) |
| Windows_8 | Microsoft | - (including) | - (including) |
| Windows_8.1 | Microsoft | - (including) | - (including) |
| Windows_rt | Microsoft | - (including) | - (including) |
| Windows_rt_8.1 | Microsoft | - (including) | - (including) |
| Windows_server_2003 | Microsoft | –sp2 (including) | –sp2 (including) |
| Windows_server_2008 | Microsoft | –sp2 (including) | –sp2 (including) |
| Windows_server_2008 | Microsoft | r2-sp1 (including) | r2-sp1 (including) |
| Windows_server_2012 | Microsoft | - (including) | - (including) |
| Windows_server_2012 | Microsoft | r2 (including) | r2 (including) |
| Windows_vista | Microsoft | –sp2 (including) | –sp2 (including) |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: