CVE Vulnerabilities

CVE-2015-7560

Improper Access Control

Published: Mar 13, 2016 | Modified: Aug 29, 2022
CVSS 3.x
6.5
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
CVSS 2.x
4 MEDIUM
AV:N/AC:L/Au:S/C:N/I:P/A:N
RedHat/V2
3.5 MODERATE
AV:N/AC:M/Au:S/C:P/I:N/A:N
RedHat/V3
Ubuntu
MEDIUM

The SMB1 implementation in smbd in Samba 3.x and 4.x before 4.1.23, 4.2.x before 4.2.9, 4.3.x before 4.3.6, and 4.4.x before 4.4.0rc4 allows remote authenticated users to modify arbitrary ACLs by using a UNIX SMB1 call to create a symlink, and then using a non-UNIX SMB1 call to write to the ACL content.

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
Samba Samba 3.2.0 (including) 4.1.23 (excluding)
Samba Samba 4.2.0 (including) 4.2.9 (excluding)
Samba Samba 4.3.0 (including) 4.3.6 (excluding)
Samba Samba 4.4.0-rc1 (including) 4.4.0-rc1 (including)
Samba Samba 4.4.0-rc2 (including) 4.4.0-rc2 (including)
Samba Samba 4.4.0-rc3 (including) 4.4.0-rc3 (including)
Samba Ubuntu devel *
Samba Ubuntu precise *
Samba Ubuntu trusty *
Samba Ubuntu wily *
Samba Ubuntu xenial *
Samba Ubuntu yakkety *
Samba Ubuntu zesty *
Samba4 Ubuntu precise *
Red Hat Enterprise Linux 6 RedHat samba-0:3.6.23-25.el6_7 *
Red Hat Enterprise Linux 6 RedHat samba4-0:4.0.0-68.el6_7.rc4 *
Red Hat Enterprise Linux 7 RedHat samba-0:4.2.3-12.el7_2 *
Red Hat Gluster Storage 3.1 for RHEL 6 RedHat samba-0:4.2.4-15.el6rhs *
Red Hat Gluster Storage 3.1 for RHEL 7 RedHat samba-0:4.2.4-15.el7rhgs *

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