Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 418
  • Last Modified:

SQL 'sa' logon attempts

Hello,

    I have a Windows Server 2008 R2 box running IIS 7.0 and SQL 2008 R2. I have a Juniper firewall protecting my server but we do have port 80 open to the Internet because we require it. My IIS logs are pretty mild. I have a few script attempts here and there, but my SQL logs are flooded (1000+/day) with 'sa' logon attempts.

     How is my SQL server getting hit without my IIS Server logging it?
0
FNDAdmin
Asked:
FNDAdmin
  • 4
  • 4
  • 3
  • +2
3 Solutions
 
Carl TawnSystems and Integration DeveloperCommented:
That might suggest that the attempts are coming from somewhere other than through the web server. Does the SQL log show the attempt as coming from your IIS server?
0
 
FNDAdminAuthor Commented:
Date            12/4/2013 3:28:02 PM
Log            SQL Server (Current - 12/3/2013 4:25:00 PM)
Source            Logon
Message
Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 116.255.197.205]

SQL Logs do not indicate _where_ the attempts are coming through.
0
 
Carl TawnSystems and Integration DeveloperCommented:
The IP in the message is the source of the attempt - is that the IP of the SQL server, or the web server (or are they both on the same box)?

I'd suggest running a trace for the "Audit Login" and "Audit Login Failed" event classes, and make sure to include both the DatabaseID and the Application Name fields.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Dave BaldwinFixer of ProblemsCommented:
116.255.197.205 is coming from ZhengZhou GIANT Computer Network Technology Co., Ltd in China.
0
 
MajorBigDealCommented:
http://whois.net/ip-address-lookup/

shows that address is:

ZhengZhou GIANT Computer Network Technology Co., Ltd
descr:          Room 701, Information Building NO.144 Garden Road,
descr:          Zhenzhou, Henan, P.R.China
0
 
FNDAdminAuthor Commented:
Correct. the only reason I pasted a valid IP address into this forum is because it is NOT mine. It is the script kiddie hitting my box.

Thank you to those that did a WHOIS look up on it.

Carl, as soon as I posted that questions I started a trace. I modified it to include the columns there were not by default selected. I'll let it run through the night and see what it comes up with in the morning.

I have since put in a request to my firewall guy to change the port 80 scope to allow USA based IP Address ranges only.
I'll provide an update tomorrow
0
 
MajorBigDealCommented:
I think your original question about why it did not show up in your web server logs is key.  I'd be concerned that they have already compromised your web server and are deleting the log entries or otherwise preventing them from showing up.  

I think it is good to limit to US addresses but that won't stop them.  For example, they could use a VPN service to make it look like they are in the US, and I'm sure they know other ways to get around it as well.
0
 
Dave BaldwinFixer of ProblemsCommented:
I think they are going directly to your SQL Server which is on a different port than the web server.  Which is why it does not show in the web server logs.
0
 
MajorBigDealCommented:
If Dave is right and someone is able to issue requests directly from the internet to your SQL server that seems like a huge problem to me.   Maybe you can configure a whitelist on your sql server so that it only accepts traffic from localhost or other known authorized servers?
0
 
FNDAdminAuthor Commented:
SQL, TCP1033, is not accessible from the Internet. Only port 80 is 'open'.
0
 
Dave BaldwinFixer of ProblemsCommented:
You might want to double check that.  SQL Server can use multiple ports and 1433 is the 'standard' port.  1434 is used by the SQL Browser service if you have that enabled.

And the fact that the failed connection is from an IP address from China means that it is Not coming from your web server which would be on your IP address.
0
 
FNDAdminAuthor Commented:
I am sorry, I mis-typed, Our SQL Server is configured to used the standard/default port, of 1433 for communications.

     I receive information from our firewall people that SQL 1433 _WAS_ open to the Internet. I cannot believe they let that one slip by them. It has since been closed and the event logs are back to normal.

    Thank you all for your help.
0
 
Dave BaldwinFixer of ProblemsCommented:
You're welcome, glad to help.  Thanks for the points.
0
 
Animesh KumarCommented:
We are facing the same problem (SQL 'sa' logon attempts) but it is comming from our Web Server. I am a System Admin. Kindly let me know how to resolve the problem.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 4
  • 3
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now