CVE Vulnerabilities

CVE-2023-4091

Incorrect Default Permissions

Published: Nov 03, 2023 | Modified: Sep 16, 2024
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
RedHat/V2
RedHat/V3
6.5 MODERATE
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Ubuntu
MEDIUM

A vulnerability was discovered in Samba, where the flaw allows SMB clients to truncate files, even with read-only permissions when the Samba VFS module acl_xattr is configured with acl_xattr:ignore system acls = yes. The SMB protocol allows opening files when the client requests read-only access but then implicitly truncates the opened file to 0 bytes if the client specifies a separate OVERWRITE create disposition request. The issue arises in configurations that bypass kernel file system permissions checks, relying solely on Sambas permissions.

Weakness

During installation, installed file permissions are set to allow anyone to modify those files.

Affected Software

Name Vendor Start Version End Version
Samba Samba * 4.17.12 (excluding)
Samba Samba 4.18.0 (including) 4.18.8 (excluding)
Samba Samba 4.19.0 (including) 4.19.1 (excluding)
Red Hat Enterprise Linux 8 RedHat samba-0:4.18.6-2.el8_9 *
Red Hat Enterprise Linux 8 RedHat samba-0:4.18.6-2.el8_9 *
Red Hat Enterprise Linux 8.6 Extended Update Support RedHat samba-0:4.15.5-13.el8_6 *
Red Hat Enterprise Linux 8.8 Extended Update Support RedHat samba-0:4.17.5-4.el8_8 *
Red Hat Enterprise Linux 9 RedHat samba-0:4.18.6-101.el9_3 *
Red Hat Enterprise Linux 9 RedHat samba-0:4.18.6-101.el9_3 *
Red Hat Enterprise Linux 9.0 Extended Update Support RedHat samba-0:4.15.5-111.el9_0 *
Red Hat Enterprise Linux 9.2 Extended Update Support RedHat samba-0:4.17.5-104.el9_2 *
Red Hat Virtualization 4 for Red Hat Enterprise Linux 8 RedHat samba-0:4.15.5-13.el8_6 *
Samba Ubuntu bionic *
Samba Ubuntu devel *
Samba Ubuntu focal *
Samba Ubuntu jammy *
Samba Ubuntu lunar *
Samba Ubuntu mantic *
Samba Ubuntu noble *
Samba Ubuntu oracular *
Samba Ubuntu trusty *
Samba Ubuntu xenial *

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