The remote Scientific Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the SLSA-2021:5192-1 advisory.

  - samba: Active Directory (AD) domain user could become root on domain members (CVE-2020-25717)

  - samba: SMB1 client connections can be downgraded to plaintext authentication (CVE-2016-2124)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote CentOS Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the CESA-2021:5082 advisory.

  - samba: SMB1 client connections can be downgraded to plaintext authentication (CVE-2016-2124)

  - samba: Active Directory (AD) domain user could become root on domain members (CVE-2020-25717)

  - samba: Subsequent DCE/RPC fragment injection vulnerability (CVE-2021-23192)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

According to the versions of the samba packages installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

  - A flaw was found in the way samba implemented SMB1 authentication. An attacker could use this flaw to     retrieve the plaintext password sent over the wire even if Kerberos authentication was required.
    (CVE-2016-2124)

  - A flaw was found in the way Samba maps domain users to local users. An authenticated attacker could use     this flaw to cause possible privilege escalation. (CVE-2020-25717)

  - A flaw was found in the way samba, as an Active Directory Domain Controller, is able to support an RODC     (read-only domain controller). This would allow an RODC to print administrator tickets. (CVE-2020-25718)

  - A flaw was found in the way Samba, as an Active Directory Domain Controller, implemented Kerberos name-     based authentication. The Samba AD DC, could become confused about the user a ticket represents if it did     not strictly require a Kerberos PAC and always use the SIDs found within. The result could include total     domain compromise. (CVE-2020-25719)

  - Kerberos acceptors need easy access to stable AD identifiers (eg objectSid). Samba as an AD DC now     provides a way for Linux applications to obtain a reliable SID (and samAccountName) in issued tickets.
    (CVE-2020-25721)

  - Multiple flaws were found in the way samba AD DC implemented access and conformance checking of stored     data. An attacker could use this flaw to cause total domain compromise. (CVE-2020-25722)

  - A null pointer de-reference was found in the way samba kerberos server handled missing sname in TGS-REQ     (Ticket Granting Server - Request). An authenticated user could use this flaw to crash the samba server.
    (CVE-2021-3671)

  - In DCE/RPC it is possible to share the handles (cookies for resource state) between multiple connections     via a mechanism called 'association groups'. These handles can reference connections to our sam.ldb     database. However while the database was correctly shared, the user credentials state was only pointed at,     and when one connection within that association group ended, the database would be left pointing at an     invalid 'struct session_info'. The most likely outcome here is a crash, but it is possible that the use-     after-free could instead allow different user state to be pointed at and this might allow more privileged     access. (CVE-2021-3738)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote Rocky Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RLSA-2021:5082 advisory.

  - A flaw was found in the way samba implemented SMB1 authentication. An attacker could use this flaw to     retrieve the plaintext password sent over the wire even if Kerberos authentication was required.
    (CVE-2016-2124)

  - A flaw was found in the way Samba maps domain users to local users. An authenticated attacker could use     this flaw to cause possible privilege escalation. (CVE-2020-25717)

  - A flaw was found in the way samba implemented DCE/RPC. If a client to a Samba server sent a very large     DCE/RPC request, and chose to fragment it, an attacker could replace later fragments with their own data,     bypassing the signature requirements. (CVE-2021-23192)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SUSE15 host has packages installed that are affected by multiple vulnerabilities as referenced in the openSUSE-SU-2021:3650-1 advisory.

  - An attacker can downgrade a negotiated SMB1 client connection and its capabitilities. Kerberos     authentication is only possible with the SMB2/3 protocol or SMB1 using the NT1 dialect and the extended     security (spnego) capability. Without mandatory SMB signing the protocol can be downgraded to an older     insecure dialect like CORE, COREPLUS/CORE+, LANMAN1 or LANMAN2. Even if SMB signing is required it's still     possible to downgrade to the NT1 dialect if extended security (spnego) is not negotiated. The attacker is     able to get the plaintext password sent over the wire even if Kerberos authentication was required. The     problem is only possible if all of the following options are explicitly set together: client NTLMv2 auth =     no client lanman auth = yes client plaintext auth = yes client min protocol = NT1 # or lower In currently     supported Samba versions all of the above options have different default values, so the problem is very     unlikely to happen. Samba 4.5 and older had an additional problem, even in the default configuration, as     they send ntlmv2, ntlm or lanman responses. Which means the attacker might be able to do offline attacks     in order to recover the plaintext password, lmhash or nthash values. Requiring Kerberos authentication for     SMB1/2/3 connections can be controlled by the '-k'/'--kerberos' or '-k yes'/'--kerberos=yes' command line     options of various tools like: smbclient, smbcquotas, smbcacls, net, rpcclient, samba-tool and others.
    Note that 4.15 deprecated '-k/--kerberos*' and introduced '--use-kerberos=required' command line option as     well as the smb.conf option client use kerberos = required. For libsmbclient based applications the     usage of Kerberos is controlled by the following function calls: smbc_setOptionUseKerberos(),     smbc_setOptionFallbackAfterKerberos() and smbc_setOptionNoAutoAnonymousLogin(). (CVE-2016-2124)

  - Windows Active Directory (AD) domains have by default a feature to allow users to create computer     accounts, controlled by ms-DS-MachineAccountQuota. In addition some (presumably trusted) users have the     right to create new users or computers in both Samba and Windows Active Directory Domains. These features     can be quite dangerous in the wrong hands, as the user who creates such accounts has broad privileges to     not just create them and set their passwords, but to rename them at a later time with the only contraint     being they may not match an existing samAccountName in AD. When Samba as an AD Domain member accepts a     Kerberos ticket, it must map the information found therein to a local UNIX user-id (uid). This is     currently done via the account name in the Active Directory generated Kerberos Privileged Attribute     Certificate (PAC), or the account name in the ticket (if there is no PAC). For example, Samba will attempt     to find a user DOMAIN\user before falling back to trying to find the user user. If the DOMAIN\user     lookup can be made to fail, then a privilege escalation is possible. The easiest example to illustrate     this is if an attacker creates an account named root (by renaming a MachineAccountQuota based machine     account), and asks for a login without a Kerberos PAC. Between obtaining the ticket and presenting it to a     server, the attacker renames the user account to a different name. Samba attempts to look up     DOMAIN\root, which fails (as this no longer exists) and then falls back to looking up user root, which     will map to the privileged UNIX uid of 0. This patch changes Samba to require a PAC (in all scenarios     related to active directory domains) and use the SID and account name values of the PAC, which means the     combination represents the same point in time. The processing is now similar to as with NTLM based logins.
    The SID is unique and non-repeating and so can't be confused with another user. Additionally, a new     parameter has been added min domain uid (default 1000), and no matter how we obtain the UNIX uid to use     in the process token (we may eventually read /etc/passwd or similar), by default no UNIX uid below this     value will be accepted. The patch also removes the fallback from 'DOMAIN\user' to just 'user', as it     dangerous and not needed when nss_winbind is used (even when 'winbind use default domain = yes' is set).
    However there are setups which are joined to an active directory domain just for authentication, but the     authorization is handled without nss_winbind by mapping the domain account to a local user provided by     nss_file, nss_ldap or something similar. NOTE: These setups won't work anymore without explicitly mapping     the users! For these setups administrators need to use the 'username map' or 'username map script' option     in order to map domain users explicitly to local users, e.g. user = DOMAIN\user Please consult 'man 5     smb.conf' for further details on 'username map' or 'username map script'. Also note that in the above     example '\' refers to the default value of the 'winbind separator' option. (CVE-2020-25717)

  - Samba implements DCE/RPC, and in most cases it is provided over and protected by the underlying SMB     transport, with protections like 'SMB signing'. However there are other cases where large DCE/RPC request     payloads are exchanged and fragmented into several pieces. If this happens over untrusted transports (e.g.
    directly over TCP/IP or anonymous SMB) clients will typically protect by an explicit authentication at the     DCE/RPC layer, e.g. with GSSAPI/Kerberos/NTLMSSP or Netlogon Secure Channel. Because the checks on the     fragment protection were not done between the policy controls on the header and the subsequent fragments,     an attacker could replace subsequent fragments in requests with their own data, which might be able to     alter the server behaviour. DCE/RPC is a core component of all Samba servers, but we are most concerned     about Samba as a Domain Controller, given the role as a centrally trusted service. As active directory     domain controller this issue affects Samba versions greater or equal to 4.10.0. As NT4 classic domain     controller, domain member or standalone server this issue affects Samba versions greater or equal to     4.13.0. (CVE-2021-23192)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 8 host has a package installed that is affected by a vulnerability as referenced in the RHSA-2022:0133 advisory.

    The redhat-virtualization-host packages provide the Red Hat Virtualization Host. These packages include     redhat-release-virtualization-host, ovirt-node, and rhev-hypervisor. Red Hat Virtualization Hosts (RHVH)     are installed using a special build of Red Hat Enterprise Linux with only the packages required to host     virtual machines. RHVH features a Cockpit user interface for monitoring the host's resources and     performing administrative tasks.

    Security Fix(es):

    * samba: Active Directory (AD) domain user could become root on domain members (CVE-2020-25717)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

According to the versions of the samba packages installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

  - A flaw was found in the way samba implemented SMB1 authentication. An attacker could use this flaw to     retrieve the plaintext password sent over the wire even if Kerberos authentication was required.
    (CVE-2016-2124)

  - A flaw was found in the way Samba maps domain users to local users. An authenticated attacker could use     this flaw to cause possible privilege escalation. (CVE-2020-25717)

  - A null pointer de-reference was found in the way samba kerberos server handled missing sname in TGS-REQ     (Ticket Granting Server - Request). An authenticated user could use this flaw to crash the samba server.
    (CVE-2021-3671)

  - The Samba vfs_fruit module uses extended file attributes (EA, xattr) to provide '...enhanced compatibility     with Apple SMB clients and interoperability with a Netatalk 3 AFP fileserver.' Samba versions prior to     4.13.17, 4.14.12 and 4.15.5 with vfs_fruit configured allow out-of-bounds heap read and write via     specially crafted extended file attributes. A remote attacker with write access to extended file     attributes can execute arbitrary code with the privileges of smbd, typically root. (CVE-2021-44142)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The version of samba installed on the remote host is prior to 4.10.16-18. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2022-1746 advisory.

    Out-of-bounds heap read/write vulnerability in VFS module vfs_fruit allows code execution (CVE-2021-44142)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Published	Updated	Severity
156178	Scientific Linux Security Update : samba on SL7.x i686/x86_64 (2021:5192)	Nessus	Scientific Linux Local Security Checks	12/18/2021	2/28/2022	high
156238	CentOS 8 : samba (CESA-2021:5082)	Nessus	CentOS Local Security Checks	12/21/2021	2/28/2022	high
159868	EulerOS Virtualization 2.10.0 : samba (EulerOS-SA-2022-1413)	Nessus	Huawei Local Security Checks	4/18/2022	11/8/2022	high
184610	Rocky Linux 8 : samba (RLSA-2021:5082)	Nessus	Rocky Linux Local Security Checks	11/6/2023	11/6/2023	high
155191	openSUSE 15 Security Update : samba (openSUSE-SU-2021:3650-1)	Nessus	SuSE Local Security Checks	11/11/2021	2/28/2022	high
156736	RHEL 8 : Red Hat Virtualization Host security update [ovirt-4.4.9] Async #2 (Important) (RHSA-2022:0133)	Nessus	Red Hat Local Security Checks	1/13/2022	11/7/2024	high
165891	EulerOS Virtualization 3.0.6.6 : samba (EulerOS-SA-2022-2537)	Nessus	Huawei Local Security Checks	10/9/2022	2/3/2023	high
157885	Amazon Linux 2 : samba (ALAS-2022-1746)	Nessus	Amazon Linux Local Security Checks	2/11/2022	12/11/2024	high

Detections

Analytics

Plugins Search

high

high

high

high

high

high

high

high