CVE Vulnerabilities

CVE-2015-5116

Improper Access Control

Published: Jul 09, 2015 | Modified: Sep 22, 2017
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
Ubuntu

Adobe Flash Player before 13.0.0.302 and 14.x through 18.x before 18.0.0.203 on Windows and OS X and before 11.2.202.481 on Linux, Adobe AIR before 18.0.0.180, Adobe AIR SDK before 18.0.0.180, and Adobe AIR SDK & Compiler before 18.0.0.180 allow remote attackers to bypass the Same Origin Policy via unspecified vectors, a different vulnerability than CVE-2014-0578, CVE-2015-3115, CVE-2015-3116, and CVE-2015-3125.

Weakness

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Affected Software

Name Vendor Start Version End Version
Flash_player Adobe * 13.0.0.289
Flash_player Adobe 14.0.0.125 14.0.0.125
Flash_player Adobe 14.0.0.145 14.0.0.145
Flash_player Adobe 14.0.0.176 14.0.0.176
Flash_player Adobe 14.0.0.179 14.0.0.179
Flash_player Adobe 15.0.0.152 15.0.0.152
Flash_player Adobe 15.0.0.167 15.0.0.167
Flash_player Adobe 15.0.0.189 15.0.0.189
Flash_player Adobe 15.0.0.223 15.0.0.223
Flash_player Adobe 15.0.0.239 15.0.0.239
Flash_player Adobe 15.0.0.246 15.0.0.246
Flash_player Adobe 16.0.0.235 16.0.0.235
Flash_player Adobe 16.0.0.257 16.0.0.257
Flash_player Adobe 16.0.0.287 16.0.0.287
Flash_player Adobe 16.0.0.296 16.0.0.296
Flash_player Adobe 17.0.0.134 17.0.0.134
Flash_player Adobe 17.0.0.169 17.0.0.169
Flash_player Adobe 17.0.0.188 17.0.0.188
Flash_player Adobe 17.0.0.190 17.0.0.190
Flash_player Adobe 18.0.0.160 18.0.0.160
Flash_player Adobe 18.0.0.194 18.0.0.194

Extended Description

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:

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References