[sqlmap-users] Bug in sqlmap in Microsoft SQL Server

[Rodrigo Z. S. <rod...@gm...>]

I finally discovery why the program wasn't working. I was trying to use in
a table and it use the default:

where column_name > (char string)

So the program get the next element testing if it is bigger than previous.
So it get the name:

JOAO

To get the next, the sqlmap create:

 WHERE
CONVERT(NVARCHAR(4000),tablename)>CHAR(74)+CHAR(79)+CHAR(65)+CHAR(79))

So the next it get is:

JOĂO

So, this is a problem. I just see now that I need to configure the
encoding. But the caracter it get was Ă (wiki
<https://en.wikipedia.org/wiki/%C4%82>), but the real character in
portuguese language is à (wiki <https://en.wikipedia.org/wiki/%C3%83>) and
now the sqlmap do this:

WHERE CONVERT(NVARCHAR(4000),tablename)>CHAR(74)+CHAR(79)+*NCHAR(258)*
+CHAR(79)

The problem is it now only get the JOĂO. He did a wrong encode. Because the
program try to get the next with a bigger then, if it get the same result
it is obvious a error. So why not ask to user to choose another encode, or
maybe ask if he want put the next string to try to get a bigger than that.

The worst thing is getting the same thing all times. No one want it.

By the way, I solved the problem putting a --charset=ISO-8859-1