SQL Injection attacks are a method where attackers can seed malware on a vulnerable site that may not be programmed with effective controls.  Sometimes input strings can be manipulated allowing unauthorized objects to be written to a public area on the server.  These objects can then be scripted in attacks so that users are redirected unknowingly to other malicious websites.  Corporations can address this will tools that identify vulnerable sites and having their developers strength controls to prevent automated attacks and seeding of malware.

SQL Injection Attacks – Corporate Need to address weaknesses

QUOTE:  SQL injection vulnerabilities have really been around for ages – the first reference I can remember of was Rain Forest Puppy’s article for Phrack 54 “NT Web Technology Vulnerabilities” that was published back in 1998 (yes – SQL injection is almost 13 years old!). However, as we can see from the examples that happened recently (and from many other cases – just take a look at the mass SQL injection attacks that are performed automatically by malware these days) SQL injection vulnerabilities are unfortunately here to stay.

So are the bad guys any better? Unfortunately, the answer is YES. When I get my hands on, I always try to analyze server side scripts that the bad guys use – these are usually scripts running on their C&C servers that help them control infected machine, issue and schedule tasks and so on.  So, if the bad guys can do it, we should be better to – so please use couple of minutes to educate your developers about the dangers of writing insecure code.