CVE Vulnerabilities

CVE-2018-16838

Improper Access Control

Published: Mar 25, 2019 | Modified: Nov 21, 2024
CVSS 3.x
5.4
MEDIUM
Source:
NVD
CVSS:3.0/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 LOW
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Ubuntu
LOW
root.io logo minimus.io logo echo.ai logo

A flaw was found in sssd Group Policy Objects implementation. When the GPO is not readable by SSSD due to a too strict permission settings on the server side, SSSD will allow all authenticated users to login instead of denying access.

Weakness

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

Affected Software

NameVendorStart VersionEnd Version
SssdFedoraproject- (including)- (including)
Red Hat Enterprise Linux 7RedHatsssd-0:1.16.4-21.el7*
Red Hat Enterprise Linux 8RedHatsssd-0:2.2.0-19.el8*
Red Hat Virtualization 4 for Red Hat Enterprise Linux 7RedHatimgbased-0:1.1.9-0.1.el7ev*
Red Hat Virtualization 4 for Red Hat Enterprise Linux 7RedHatovirt-node-ng-0:4.3.5-0.20190717.0.el7ev*
Red Hat Virtualization 4 for Red Hat Enterprise Linux 7RedHatredhat-release-virtualization-host-0:4.3.5-2.el7ev*
Red Hat Virtualization 4 for Red Hat Enterprise Linux 7RedHatredhat-virtualization-host-0:4.3.5-20190722.0.el7_7*
SssdUbuntubionic*
SssdUbuntucosmic*
SssdUbuntudisco*
SssdUbuntuesm-infra/bionic*
SssdUbuntuesm-infra/xenial*
SssdUbuntutrusty*
SssdUbuntuupstream*
SssdUbuntuxenial*

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