Fixing 'SMB Signing Disabled or SMB Signing Not Required' vulnerability.

-

If your organization is using a vulnerability scanning tool then more often than not, vulnerability like SMB Signing Disabled or SMB Signing Not Required will flag up and probably make it to the top of the list. This is because most organizations may not have SMB signing enabled by default for all their client and server communications.


What is SMB signing?

SMB signing is a security mechanism in the SMB protocol which is designed to help improve the security of the SMB protocol. SMB signing adds security to a network using NetBIOS, avoiding man-in-the-middle attacks and when enabled on both the client and server, SMB sessions are authenticated between the machines on the packet level.


According to Microsoft, following SMB configuration scenarios can play out -

If SMB Signing is enabled and required at both the client and the server, or if SMB signing is disabled at both the client and the server, the connection is successful.

If SMB signing is enabled and required at the client and disabled at the server, the connection to the TCP session is gracefully closed after the Dialect Negotiation, and the client receives the following "1240 (ERROR_LOGIN_WKSTA_RESTRICTION)" error message:

System error 1240 has occurred. The account is not authorized to log in from this station.

If SMB signing is disabled at the client and enabled and required at the server, the client receives the "STATUS_ACCESS_DENIED" error message when it receives a response to a Tree Connect or Transact2 for DFS referrals.

How to fix the vulnerability?

While GPO is the preferred way to configure the SMB configuration settings, one can set the desired registry values to achieve the same. I will cover both these methods in this blog.

Setting registry values -

If you manage your servers using an On-prem infrastructure management tool like ConfigMgr, then you can easily set the registry values using compliance baseline settings.

The registry values that I am setting will ensure that SMB signing is enabled and required on both Clients and Servers at all times. This is in line with the requirement for vulnerability I am addressing under QID 90043. 

Please note that this configuration can have serious implications, therefore please use this configuration in accordance to your infrastructure setup and requirements. Also, ensure that your GPO policies are in line with the settings below or else GPO will take precedence.

HKLM\System\CurrentControlSet\Services\LanManWorkstation\Parameters requiresecuritysignature = 1

HKLM\System\CurrentControlSet\Services\LanManServer\Parameters requiresecuritysignature = 1

HKLM\System\CurrentControlSet\Services\LanManSever\Parameters enablesecuritysignature = 1

HKLM\System\CurrentControlSet\Services\LanManWorkstation\Parameters enablesecuritysignature = 1


The CI in ConfigMgr will look something like this -

For setting HKLM\System\CurrentControlSet\Services\LanManSever\Parameters enablesecuritysignature = 1





For setting HKLM\System\CurrentControlSet\Services\LanManWorkstation\Parameters enablesecuritysignature = 1





For setting HKLM\System\CurrentControlSet\Services\LanManServer\Parameters requiresecuritysignature = 1





For setting HKLM\System\CurrentControlSet\Services\LanManWorkstation\Parameters requiresecuritysignature = 1





After the CI is created, deploy it in a baseline with remediation enabled.


Setting Group Policy -

In Group Policy Management, navigate to the location Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options for the intended policy and Enable the following settings.


Conclusion

It is important to enable SMB signing as attackers can potentially intercept the traffic after gaining unauthorized access to the network and modify unsigned Server Message Block (SMB) packets. They can perform session hijacking, posing as the server or client device using a legitimate authentication session and gain unauthorized access to data.

Comments

Post a Comment

Popular posts from this blog

How to force escrowing of BitLocker recovery keys using Intune

-
Image
Every now and then it so happens that BitLocker recovery keys do not escrow in AAD. The usual culprits are incorrect BitLocker policies and\or the device hardware configuration failing to meet the minimum requirements. The other scenario and something I recently experienced is when everything is setup right and still the recovery key doesn’t escrow in AAD. As I understand, this can happen if the escrow process got interrupted the first time due to network or local devices related issues and the process could not resume. To circumvent this issue, one can simply push a PowerShell script to the devices to force the escrow of the recovery keys to AAD. Here is a script to do so. try{ $BitlockerVol = Get-BitLockerVolume -MountPoint $env:SystemDrive         $KPID=""         foreach($KP in $BitlockerVol.KeyProtector){             if($KP.KeyProtectorType -eq "RecoveryPassword"){                 $KPID=$KP.KeyProtectorId                 break;             }         }        $o
Read more

Intune: Configure Printers for Non-Administrative Users

-
Image
Configuring printers for end users or giving them the ability to do it themselves is a normal requirement for organizations. Now if your users are Administrators, then the configuration can be straight forward, but in case of Non-Administrators there are additional steps required as Non-Administrators will not be able to add a driver in the driver store despite being able to install a printer. In this blog, I will cover the steps that I took to address this requirement using Intune. The setup involves 2 steps -  1. Setup registries. 2. Install the driver and configure the printer Setting up registries – The registries that need to be configured are actually part of a GPO setting – Allow non-administrators to install drivers for these device setup classes It can be found under: Computer Configuration -> Policies -> Administrative Templates -> System -> Driver Installation I used a Powershell script to set the values and wrapped it in a Win32 application. $Path1
Read more

Intune: UAC Elevation Prompt Behavior for Standard Users

-
Image
Implementing and maintaining a good security posture is an integral part of overall IT security governance for most organizations now. While you want to harden the security of infrastructure and give least number of privileges to your end users, sometimes you may need to cut back on the restrictions to ensure a good user experience and an effective IT support process. Recently, I had a requirement where the customer wanted to ease the restriction on the end user devices to make the helpdesk support process more efficient. This involved easing the UAC level access for the Standard users and if you are managing your devices using Intune, then this blog may just help you. Let us see what all is involved and some of the ways that you can use to implement this easily. Policy CSP – LocalPoliciesSecurityOptions LocalPoliciesSecurityOptions has many CSP settings and if you are managing these settings at an individual level, then the CSP that we need to concern ourselves with here is U
Read more