Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160, Adobe AIR before 18.0.0.144, Adobe AIR SDK before 18.0.0.144, and Adobe AIR SDK & Compiler before 18.0.0.144 on 64-bit Windows 7 systems do not properly select a random memory address for the Flash heap, which makes it easier for attackers to conduct unspecified attacks by predicting this address.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Air | Adobe | * | 17.0.0.172 (including) |
| Air_sdk | Adobe | * | 17.0.0.172 (including) |
| Air_sdk_&_compiler | Adobe | * | 17.0.0.172 (including) |
| Flash_player | Adobe | * | 13.0.0.289 (including) |
| Flash_player | Adobe | 14.0.0.125 (including) | 14.0.0.125 (including) |
| Flash_player | Adobe | 14.0.0.145 (including) | 14.0.0.145 (including) |
| Flash_player | Adobe | 14.0.0.176 (including) | 14.0.0.176 (including) |
| Flash_player | Adobe | 14.0.0.179 (including) | 14.0.0.179 (including) |
| Flash_player | Adobe | 15.0.0.152 (including) | 15.0.0.152 (including) |
| Flash_player | Adobe | 15.0.0.167 (including) | 15.0.0.167 (including) |
| Flash_player | Adobe | 15.0.0.189 (including) | 15.0.0.189 (including) |
| Flash_player | Adobe | 15.0.0.223 (including) | 15.0.0.223 (including) |
| Flash_player | Adobe | 15.0.0.239 (including) | 15.0.0.239 (including) |
| Flash_player | Adobe | 15.0.0.246 (including) | 15.0.0.246 (including) |
| Flash_player | Adobe | 16.0.0.235 (including) | 16.0.0.235 (including) |
| Flash_player | Adobe | 16.0.0.257 (including) | 16.0.0.257 (including) |
| Flash_player | Adobe | 16.0.0.287 (including) | 16.0.0.287 (including) |
| Flash_player | Adobe | 16.0.0.296 (including) | 16.0.0.296 (including) |
| Flash_player | Adobe | 17.0.0.134 (including) | 17.0.0.134 (including) |
| Flash_player | Adobe | 17.0.0.169 (including) | 17.0.0.169 (including) |
| Flash_player | Adobe | 17.0.0.188 (including) | 17.0.0.188 (including) |
| Adobe-flashplugin | Ubuntu | devel | * |
| 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 | * |
There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:
Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:
Information exposures can occur in different ways:
It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.