Race condition in Adobe Flash Player before 13.0.0.289 and 14.x through 17.x before 17.0.0.188 on Windows and OS X and before 11.2.202.460 on Linux, Adobe AIR before 17.0.0.172, Adobe AIR SDK before 17.0.0.172, and Adobe AIR SDK & Compiler before 17.0.0.172 allows attackers to bypass the Internet Explorer Protected Mode protection mechanism via unspecified vectors.
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 |
|---|---|---|---|
| Flash_player | Adobe | * | 11.2.202.475 (including) |
| Adobe-flashplugin | Ubuntu | precise | * |
| Adobe-flashplugin | Ubuntu | trusty | * |
| Adobe-flashplugin | Ubuntu | upstream | * |
| Adobe-flashplugin | Ubuntu | utopic | * |
| Adobe-flashplugin | Ubuntu | vivid | * |
| Flashplugin-nonfree | Ubuntu | devel | * |
| Flashplugin-nonfree | Ubuntu | precise | * |
| Flashplugin-nonfree | Ubuntu | trusty | * |
| Flashplugin-nonfree | Ubuntu | upstream | * |
| Flashplugin-nonfree | Ubuntu | utopic | * |
| Flashplugin-nonfree | Ubuntu | vivid | * |
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.