In the [previous][1] post I have written about a simple method of deterring automated tools like sqlmap
from being run against your application. I have argued that having some client-side JavaScript code that dynamically mangles form fields' name attribute can help a lot (prevent automated calls to DB via your app) when it comes to SQL-injection discovery (provided that the attacker is not-so-determined). Now let's take another side - one of an attacker - and try to circumvent that protection.
First of all, one has to determine what is actually being sent to the server in the end. In the [example][2] from the aforementioned [post][1] we have simulated a very simple mechanism implemented at the client side:
function submitForm()
{
var u = document.getElementById('username');
var p = document.getElementById('password');
var ts = (new Date()).getTime().toString().substr(0, 10);