Testing for Code Injection (OWASP-DV-012)

Revision as of 09:55, 20 November 2006 by Mmeucci (Talk | contribs)

Jump to: navigation, search

OWASP Testing Guide v2 Table of Contents


Brief Summary

This section describes how a tester can check if it is possible to enter code as input on a web page and have it executed by the web server.

Description of the Issue

Code Injection testing involve a tester submitting code as input that is processed by the web server as dynamic code or as in an included file. These tests can target various server side scripting engines, i.e. ASP, PHP, etc. Proper validation and secure coding practices need to be employed to protect against these attacks.

Black Box testing and example

Testing for PHP Injection vulnerabilities:

Using the querystring, the tester can inject code (in this example, a malicious url) to be processed as part of the included file:


Result Expected:

The malicious URL is accepted as a parameter for the PHP page, which will later use the value in an include file.

Gray Box testing and example

Testing for ASP Code Injection vulnerabilities

Examining ASP code for user input used in execution functions, e.g. Can the user enter commands into the Data input field? Here, the ASP code will save it to file and then execute it:

If not isEmpty(Request( "Data" ) ) Then
Dim fso, f
'User input Data is written to a file named data.txt
Set fso = CreateObject("Scripting.FileSystemObject")
Set f = fso.OpenTextFile(Server.MapPath( "data.txt" ), 8, True)
f.Write Request("Data") & vbCrLf
Set f = nothing
Set fso = Nothing
'Data.txt is executed
Server.Execute( "data.txt" )
<input name="Data" /><input type="submit" name="Enter Data" />
End If


OWASP Testing Guide v2

Here is the OWASP Testing Guide v2 Table of Contents