- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
FortiClient 6.4.3 detects remote.cmd.shell during SMB file copy to NAS
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
From the logs...
msg="Traffic log" sessionid=12345 srcip=x.x.x.x srcport=58664 direction=outbound dstip=y.y.y.ydstport=445 proto=6 rcvdbyte=0 sentbyte=0 utmaction=blocked utmevent=appfirewall
threat=Remote.CMD.Shell service=microsoft-ds userinitiated=0 browsetime=0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
same behavior here with FortiClient 7.0.8. Did you found any solution? I wan't to copy a virtual machine.
