Improper Access Control Affecting samba package, versions (4.17.0,4.17.2]


Severity

Recommended
0.0
medium
0
10

CVSS assessment made by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.18% (56th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Improper Access Control vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-UNMANAGED-SAMBA-3086039
  • published27 Oct 2022
  • disclosed25 Oct 2022
  • creditUnknown

Introduced: 25 Oct 2022

CVE-2022-3592  (opens in a new tab)
CWE-284  (opens in a new tab)

How to fix?

Upgrade samba to version or higher.

Overview

Affected versions of this package are vulnerable to Improper Access Control due to broken wide links protection, by allowing a user to create a symbolic link that will make smbd escape the configured share path.

Workaround

Users who are unable to upgrade to the fixed version should not enable SMB1 (please note SMB1 is disabled by default in Samba from version 4.11.0 and onwards). This prevents the creation of symbolic links via SMB1. If SMB1 must be enabled for backwards compatibility then the unix extensions = no parameter should be added to the [global] section of the smb.conf and then the smbd service has to be restarted. This prevents SMB1 clients from creating symlinks on the exported file system.

However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba it is recommended to only export areas of the file system by either SMB2 or NFS, not both.

CVSS Scores

version 3.1