CVE Vulnerabilities

CVE-2015-5053

Improper Access Control

Published: Nov 24, 2015 | Modified: Nov 21, 2024
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
10 HIGH
AV:N/AC:L/Au:N/C:C/I:C/A:C
RedHat/V2
RedHat/V3
Ubuntu
MEDIUM

The host memory mapping path feature in the NVIDIA GPU graphics driver R346 before 346.87 and R352 before 352.41 for Linux and R352 before 352.46 for GRID vGPU and vSGA does not properly restrict access to third-party device IO memory, which allows attackers to gain privileges, cause a denial of service (resource consumption), or possibly have unspecified other impact via unknown vectors related to the follow_pfn kernel-mode API call.

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
Gpu_driver Nvidia 346.16 (including) 346.16 (including)
Gpu_driver Nvidia 346.22 (including) 346.22 (including)
Gpu_driver Nvidia 346.35 (including) 346.35 (including)
Gpu_driver Nvidia 346.47 (including) 346.47 (including)
Gpu_driver Nvidia 346.59 (including) 346.59 (including)
Gpu_driver Nvidia 346.72 (including) 346.72 (including)
Gpu_driver Nvidia 346.82 (including) 346.82 (including)
Gpu_driver Nvidia 352.09 (including) 352.09 (including)
Gpu_driver Nvidia 352.21 (including) 352.21 (including)
Gpu_driver Nvidia 352.30 (including) 352.30 (including)
Gpu_driver Nvidia 352.41 (including) 352.41 (including)
Nvidia-graphics-drivers-352 Ubuntu devel *
Nvidia-graphics-drivers-352 Ubuntu upstream *
Nvidia-graphics-drivers-352 Ubuntu wily *
Nvidia-graphics-drivers-352-updates Ubuntu devel *
Nvidia-graphics-drivers-352-updates Ubuntu upstream *
Nvidia-graphics-drivers-352-updates Ubuntu wily *

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