Skip to main content
Magion
Magion
New Member
May 4, 2021
Question

FortiClient 6.4.3 detects remote.cmd.shell during SMB file copy to NAS

  • May 4, 2021
  • 2 replies
  • 4492 views

During a file copy of a vhdx file (Hyper-V VM HDD) to a NAS FortiClient suddenly terminates the connection, complaining about remote.cmd.shell detected. During the copy the FortiClient Firewall Service is actively checking the copy with high CPU usage. After the connection has been terminated, the drivemapping to the NAS is no longer accessible.

 

Why would the application firewall of FortiClient detect a remote.cmd.shell action during a regular file copy over SMB?

 

How to prevent such (false?) warnings?

    2 replies

    Magion
    MagionAuthor
    New Member
    May 4, 2021

    From the logs...

    msg="Traffic log" sessionid=12345 srcip=x.x.x.x srcport=58664 direction=outbound dstip=y.y.y.y

    dstport=445 proto=6 rcvdbyte=0 sentbyte=0 utmaction=blocked utmevent=appfirewall

    threat=Remote.CMD.Shell service=microsoft-ds userinitiated=0 browsetime=0

    padi
    padi
    Visitor III
    September 20, 2023

    Hi

    same behavior here with FortiClient 7.0.8. Did you found any solution? I wan't to copy a virtual machine.

    Terms & ConditionsAccessibility statement