Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | RE: [Snort-users] SA login failed..... |
|---|---|
| Date: | Tue, 29 Mar 2005 10:07:26 -0500 |
Do you have port 1433 open to the internet? When you make a connection to a server, your source port is random, while the destination server replies on the same port. my initial thoughts are that you have port 1433 open to the internet or to that network where the source is coming from. Depending on your firewall, I myself would re-check my fw rules and run a packet sniffer to watch the traffic coming from and to that host. It better to see it in tcpdump or tethereal versus seeing alerts in snort, you see it real-time with all relevant info Thanks, Michael Brown, _____ From: snort-users-admin@lists.sourceforge.net [mailto:snort-users-admin@lists.sourceforge.net] On Behalf Of Jeff Heckart Posted At: Tuesday, March 29, 2005 9:46 AM Posted To: Snort Conversation: SA login failed..... Subject: [Snort-users] SA login failed..... I am getting quite a few unusual alerts, and am confused with what I am seeing. The payload of the packet is: 04 01 00 3B 00 00 01 00 AA 27 00 18 48 00 00 01 ...;....*'..H... 0E 1B 00 4C 6F 67 69 6E 20 66 61 69 6C 65 64 20 ...Login failed 66 6F 72 20 75 73 65 72 20 27 73 61 27 2E 00 00 for user 'sa'... 00 00 FD 02 00 00 00 00 00 00 00 ..}........ The strange thing is that the source is: x.x.x.x:1433 (our network) Destination x.x.x.x: 2838/random (remote unknown network) This has now happened to two systems, both running mysql on tcp/1433. It just makes no sense that the source port is 1433. What am I missing here?
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Snort-users] SA login failed....., Joe Matusiewicz |
|---|---|
| Next by Date: | RE: [Snort-users] SA login failed....., Esler, Joel - Contractor |
| Previous by Thread: | RE: [Snort-users] SA login failed....., SRH-Lists |
| Next by Thread: | RE: [Snort-users] SA login failed....., Esler, Joel - Contractor |
| Indexes: | [Date] [Thread] [Top] [All Lists] |