"SMB: User Password Brute Force Attempt detected" on share that is not being accessed

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

"SMB: User Password Brute Force Attempt detected" on share that is not being accessed

L3 Networker

Recently I accessed a SMB share on a corporate Synology device (through the PA firewall). Accessing this share is hardly ever used. Now...days later, after several reboots of the client computer, the Firewall keeps on detecting the "vulnerability" SMB: User Password Brute Force Attempt(40004)

 

This is something I cannot explain. There are no active connections to this share from the client computer. There is nothing in the credential manager of Windows. There is nothing it the frequently accessed locations... Any idea why the Palo Alto would think this vulnerability is triggered an how can I find the "culprit" program which tries to access this file share?

 

Remko

1 accepted solution

Accepted Solutions

Try by running wireshark on client end to check if there are any hits to server.

M

View solution in original post

6 REPLIES 6

Cyber Elite
Cyber Elite

It seems there are still login attempts from client which is triggering child signature. Are you seeing same client IP every time?

M

Yes, according to the firewall it is the same client (IP address). 

Unfortunately I can determine what is causing the SMB traffic. There is simply nothing open on the client. 

Every 2 hours or so I see a whole bunch of warnings appear in the logs of the firewall. Then it is silent again after which the process repeats itself.

 

Very weird ?!?!?

 

Remko

Try by running wireshark on client end to check if there are any hits to server.

M

yes, this can be a way to cross verify it.

Good tip... Will do!

Wireshark reveiled that it was a webservice that tried to contact the Synology. From there, I guess it tried to open the SMB share on the computer. 

Although not visible on the computer itself it was a browser session on tcp/5000 which initiated the connection. 

  • 1 accepted solution
  • 23827 Views
  • 6 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!