Race condition in the Pragmatic General Multicast (PGM) protocol implementation in Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT Gold and 8.1, and Windows 10 Gold and 1511 allows local users to gain privileges or cause a denial of service (use-after-free) via a crafted application, aka Windows PGM UAF Elevation of Privilege Vulnerability.
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Windows_10 | Microsoft | - (including) | - (including) |
Windows_10 | Microsoft | 1511 (including) | 1511 (including) |
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_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) |
A race condition occurs within concurrent environments, and it is effectively a property of a code sequence. Depending on the context, a code sequence may be in the form of a function call, a small number of instructions, a series of program invocations, etc. A race condition violates these properties, which are closely related:
A race condition exists when an “interfering code sequence” can still access the shared resource, violating exclusivity. The interfering code sequence could be “trusted” or “untrusted.” A trusted interfering code sequence occurs within the product; it cannot be modified by the attacker, and it can only be invoked indirectly. An untrusted interfering code sequence can be authored directly by the attacker, and typically it is external to the vulnerable product.