CVE Vulnerabilities

CVE-2019-14902

Improper Access Control

Published: Jan 21, 2020 | Modified: Nov 21, 2024
CVSS 3.x
5.4
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
CVSS 2.x
5.5 MEDIUM
AV:N/AC:L/Au:S/C:P/I:P/A:N
RedHat/V2
RedHat/V3
5.4 MODERATE
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Ubuntu
LOW

There is an issue in all samba 4.11.x versions before 4.11.5, all samba 4.10.x versions before 4.10.12 and all samba 4.9.x versions before 4.9.18, where the removal of the right to create or modify a subtree would not automatically be taken away on all domain controllers.

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 4.0.0 (including) 4.9.18 (excluding)
Samba Samba 4.10.0 (including) 4.10.12 (excluding)
Samba Samba 4.11.0 (including) 4.11.5 (excluding)
Samba Ubuntu bionic *
Samba Ubuntu devel *
Samba Ubuntu disco *
Samba Ubuntu eoan *
Samba Ubuntu esm-infra-legacy/trusty *
Samba Ubuntu esm-infra/xenial *
Samba Ubuntu focal *
Samba Ubuntu groovy *
Samba Ubuntu hirsute *
Samba Ubuntu impish *
Samba Ubuntu jammy *
Samba Ubuntu kinetic *
Samba Ubuntu lunar *
Samba Ubuntu mantic *
Samba Ubuntu noble *
Samba Ubuntu oracular *
Samba Ubuntu precise/esm *
Samba Ubuntu trusty *
Samba Ubuntu trusty/esm *
Samba Ubuntu upstream *
Samba Ubuntu xenial *

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