This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit

Test Upload of Unexpected File Types (OTG-BUSLOGIC-008)

Revision as of 15:04, 22 December 2013 by David Fern (talk | contribs)

Jump to: navigation, search

Brief Description

Many application’s business processes allow for the upload and manipulation of data that is submitted via files. But the business process must check the files and only allow certain “approved” file types. The risk in that by allowing users to upload files, attackers may submit an unexpected file type that that could be executed and adversely impact the application of system through attacks such that may defacement the web site, perform remote commands, browse the system files, browse the local resources, attack other servers, or exploit the local vulnerabilities, just to name a few.

Vulnerabilities related to the upload of unexpected file types is unique in that the upload can quickly reject a file if it does not have a specific extension. Additionally, this different from uploading malicious files in that in most cases an incorrect file format may not by it self be “malicious” but may be detrimental to the saved data. For example if an application accepts Windows Excel files, if an similar database file is uploaded it may be read but data extracted my be moved to incorrect locations.


The application may be expecting only certain file types to be uploaded for processing, such as CSV files. The application may not validate the uploaded file by extension (for low assurance file validation) or content (high assurance file validation). This can result in unexpected results from the application, including other vulnerabilities discussed in other sections of the Test Guide.


Suppose a picture sharing application allows users to upload a .gif or .jpg graphic file to the web site. What if an attacker is able to upload an html file with a <script> tag in it or php file? The system may move the file from a temporary location to the final location where the php code can now be executed against the application or system.

Testing Method

Generic Testing Method

• Review the project documentation and perform some exploratory testing looking for file types that should not be "unsupported" by the application/system.

• Try to upload these “unsupported” files an verify that it are properly rejected.

• If multiple files can be uploaded at once, there must be tests in place so that each file is properly evaluated.

Specific Testing Method

• Study the applications logical requirements.

• Prepare a library of files that are “not approved” for upload that may contain files such as: jsp, exe, or html files containing script.

• In the application navigate to the file submission or upload mechanism.

• Submit the “not approved” file for upload and verify that they are properly prevented from uploading

Test Tools


Related Test Cases

4.3.3 Test File Extensions Handling for Sensitive Information (OTG-CONFIG-003)

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


OWASP - Unrestricted File Upload -

File upload security best practices: Block a malicious file upload -

Stop people uploading malicious PHP files via forms -

CWE-434: Unrestricted Upload of File with Dangerous Type -

Secure Programming Tips - Handling File Uploads -


Applications should be developed with mechanisms to only accept and manipulate “acceptable“ files that the rest of the application functionality is ready to handle and expecting. Some specific examples include: Black or White listing of file extensions, using “Content-Type” from the header, or using a file type recognizer, all to only allow specified file types into the system.