CVE Vulnerabilities

CVE-2016-7545

Improper Access Control

Published: Jan 19, 2017 | Modified: Nov 07, 2023
CVSS 3.x
8.8
HIGH
Source:
NVD
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CVSS 2.x
7.2 HIGH
AV:L/AC:L/Au:N/C:C/I:C/A:C
RedHat/V2
6.8 IMPORTANT
AV:N/AC:M/Au:N/C:P/I:P/A:P
RedHat/V3
8.6 IMPORTANT
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Ubuntu
MEDIUM

SELinux policycoreutils allows local users to execute arbitrary commands outside of the sandbox via a crafted TIOCSTI ioctl 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
Selinux Selinux_project - (including) - (including)
Red Hat Enterprise Linux 6 RedHat policycoreutils-0:2.0.83-30.1.el6_8 *
Red Hat Enterprise Linux 7 RedHat policycoreutils-0:2.5-9.el7 *
Red Hat Enterprise Linux 7.1 Extended Update Support RedHat policycoreutils-0:2.2.5-16.ael7b_1 *
Red Hat Enterprise Linux 7.2 Extended Update Support RedHat policycoreutils-0:2.2.5-21.el7_2 *
Policycoreutils Ubuntu artful *
Policycoreutils Ubuntu precise *
Policycoreutils Ubuntu trusty *
Policycoreutils Ubuntu upstream *
Policycoreutils Ubuntu yakkety *
Policycoreutils Ubuntu zesty *

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