Skip to main content

Format the drive of SQL Server ;)

I came across an interesting security issue . Not any thing special regarding the security issue but the way it was exploited was interesting. You can even fromat the hard disk of the server.
The steps were specific to that example and may not be the same in all instances. One will have to fuzz for every such attack.Steps in that example were:
1. Goto Forgot Password Feature.
2. Find a valid user id and enter a userid. A bit of guessing will work here.
3. The next screen should ask you for hint question to answer.
4. Enter SQL query to either get the password retrieved in this feature or enter incorrect SQL string to grab the server details.
5. In case the account used by application to connect to SQL server is admin account like 'sa', then MS SQL server has a feature to run kernel level commands via Extended Stored Proc.
6. Formulate a SQL query to run an extended stored procedure to run the command to format drive of SQL server.

Comments

Popular posts from this blog

SQL Injection in search field

Earlier I had written about performing SQL injection in search field and how to do a DoS attack and privilege escalation using 'Like' operators. Now another SQLi exploitation I came across recently. That too in the search field. This becomes important as lots of people don't pay much attention on the search forms/ fields in the application. My aim is to show that a search form can also be exploited with SQL Injection. The following queries are based on a real world exploitation. The steps and data are for just illustration purpose only. Suppose, the search form provides the details of users who have accessed the application some time and their login time details etc, we just need to provide their name in the search box provided. All the data were being going as Post request. So, to just fingerprint the database, I provide, 'nil'+'esh' in the search field and it successfully gives me the results. That means the database behind the application is concatenat…

File Upload through Null Byte Injection

Sometimes, during file upload we come across situation wherein there would be check on the file extension at the client side as well as server side too. If the application does allow only .jpeg extension to be uploaded, the client side java script checks for the extension of the file before passing the request. We all know that how easily this can be defeated.
Some applications, checks for the extension at the server side also. That's not easy to bypass. However there are some ways with which it still can be bypassed. Most of server side scripts are written in high level languages such as Php, Java etc who still use some C/C++ libraries to read the file name and contents. That leads to the problem. In C/C++ a line ends with /00 or which is called Null Byte. So whenever the interpreter sees a null byte at the end of the a string, it stops reading thinking it has reached at the end of the string.
This can be used for the bypass. It works for many servers, specially php servers. Th…

Insecure protocols

Some basic insecure protocols and risk associated with them: