Powered by GitBook

Owasp Testing Guide v4

Test Upload of Malicious Files (OTG-BUSLOGIC-009)

Summary

Many application’s business processes allow for the upload of data/information. We regularly check the validity and security of text but accepting files can introduce even more risk. To reduce the risk we may only accept certain file extensions, but attackers are able to encapsulate malicious code into inert file types. Testing for malicious files verifies that the application/system is able to correctly protect against attackers uploading malicious files.

Vulnerabilities related to the uploading of malicious files is unique in that these “malicious” files can easily be rejected through including business logic that will scan files during the upload process and reject those perceived as malicious. Additionally, this is different from uploading unexpected files in that while the file type may be accepted the file may still be malicious to the system.

Finally, "malicious" means different things to different systems, for example Malicious files that may exploit SQL server vulnerabilities may not be considered a "malicious" to a main frame flat file environment.

The application may allow the upload of malicious files that include exploits or shellcode without submitting them to malicious file scanning. Malicious files could be detected and stopped at various points of the application architecture such as: IPS/IDS, application server anti-virus software or anti-virus scanning by application as files are uploaded (perhaps offloading the scanning using SCAP).

Example

Suppose a picture sharing application allows users to upload their .gif or .jpg graphic files to the web site. What if an attacker is able to upload a PHP shell, or exe file, or virus? The attacker may then upload the file that may be saved on the system and the virus may spread itself or through remote processes exes or shell code can be executed.

How to Test

Generic Testing Method

  • Review the project documentation and use exploratory testing looking at the application/system to identify what constitutes and "malicious" file in your environment.
  • Develop or acquire a known “malicious” file.
  • Try to upload the malicious file to the application/system and verify that it is correctly rejected.
  • If multiple files can be uploaded at once, there must be tests in place to verify that each file is properly evaluated.

Specific Testing Method 1

  • Using the Metasploit payload generation functionality generates a shellcode as a Windows executable using the Metasploit "msfpayload" command.
  • Submit the executable via the application’s upload functionality and see if it is accepted or properly rejected.

Specific Testing Method 2

  • Develop or create a file that should fail the application malware detection process. There are many available on the Internet such as ducklin.htm or ducklin-html.htm.
  • Submit the executable via the application’s upload functionality and see if it is accepted or properly rejected.

Specific Testing Method 3

  • Set up the intercepting proxy to capture the “valid” request for an accepted file.
  • Send an “invalid” request through with a valid/acceptable file extension and see if the request is accepted or properly rejected.

Tools

  • Metasploit's payload generation functionality
  • Intercepting proxy

References

Remediation

While safeguards such as black or white listing of file extensions, using “Content-Type” from the header, or using a file type recognizer may not always be protections against this type of vulnerability. Every application that accepts files from users must have a mechanism to verify that the uploaded file does not contain malicious code. Uploaded files should never be stored where the users or attackers can directly access them.