Skip to main content

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. The high level concept is like:

1. Create a php file with any backdoor code. Numerous examples are out there on Internet.
2. Now this code PHP code needs to be merged into the .jpeg file. There are a few command line tools available on Kali, which can do it. Suppose the resultant file is Happy.jpeg. This file contains the php backdoor code also. But the we can not execute the php commands inside the Happy.jpeg file since it's and jpeg extension which the php interpreter will not understand.
3. Now here the Null byte injection works. Change the name of Happy.jpeg to Happy.phpA.jpeg. We can choose 'A', 'B' any letter. Since we all are more familiar with hex of  'A' as 41, we use that for simplicity.
4. Now upload the file. Capture the request in the Burp, switch to the Hex view. Locate the file name in the string view. See the corresponding Hex table and replace the 41 ('A') with 00 (which is null byte).
5. Now the resultant string becomes Happy.php(space) .jpeg. Now since php interpreter uses C libraries internally, it's going to stop reading the file name post Happy.php and the file will be saved as Happy.php.
6. Now thus file can be accessed depending on the path of the upload directory along with the domain name. Eg, http://domain.com/images/Happy.php and all the commands can be executed.


Comments

jhon said…
flatbed scanner except that the document is fed through the scanner and moves along the beam to be read rather than the beam moving along document. scscan

Popular posts from this blog

Ardilla- New tool for finding SQL Injection and XSS

Three Researchers -- MIT's Adam Kiezun , Stanford's Philip Guo , and Syracuse University's Karthick Jayaraman -- has developed a new tool ' Ardilla ' that automatically finds and exploits SQL injection and cross-site scripting vulnerabilities in Web applications. It creates inputs that pinpoint bugs in Web applications and then generates SQL injection and XSS attacks. But for now Ardilla is for PHP -based Web app only. The researchers say Ardilla found 68 never-before found vulnerabilities in five different PHP applications using the tool -- 23 SQL injection and 45 XSS flaws. More information is awaited. For their attack generation techniques refer to their document at: http://www.cs.washington.edu/homes/mernst/pubs/create-attacks-tr054.pdf

jtool - an alternative to otool

jtool comes with a capability of running on Linux environment. Some ipa scanning tools are created to run on Linux environment where mac environment is not available. In such cases tools such as otool and class-dump-z will not work. So jtool can be an alternative to otool. For more information on jtool please refer to http://www.newosxbook.com/tools/jtool.html . It lists down various commands which have same output as otool or a equivalent. There are several commands mentioned in link. But for our customized requirements and basis checks I have listed down the below ones after running on many binaries. The outputs are similar or equivalent to otool and class-dump-z: Commands for checking PIE flag (ASLR) in jTool jtool -d -v -arch | grep stack ·           Automatic Reference Counting (ARC) protection: jtool -d -v -arch | grep _objc_release ·           To check if the device is jailbroken: jtool -d -v -arch | grep jail ·           Dyldinfo compatible options