We have a vulnerability - "SMBv1 and SMBv2 signing not required" in WorldServer. To fix this vulnerability, we disabled SMBv1 and SMBv2 protocols on the server, but WorldServer does not share the Temporary directory (temp_file_path=D:/temp/) with another server.
So I enabled SMBv2 again and the server is able to share temporary directories. But Vulnerability is still present.
We want to eliminate the vulnerability. How can we solve this problem?
Gopichand Patil when you disable SMBv2 in certain versions of Windows Server, SMBv3 is also disabled, as they use the same stack.
Please check this article by Microsoft, in particular the part that says:
"When you enable or disable SMBv2 in Windows 8 or Windows Server 2012, SMBv3 is also enabled or disabled. This behavior occurs because these protocols share the same stack."
So, if SMB is completely disabled, then Windows sharing will not work at all. Which version of Windows Server is your WorldServer application running on?
Nick Date WorldServer application is running on Windows Server 2016
Gopichand Patil The best thing to do would be to log a support case so our support engineers can do a full investigation for you.
Thanks Nick Date for the suggestion, I have logged a support case.
Thanks Nick Date for the suggestion, I have logged a support case.
Translate
