the server hosting the target application.
■
If the first test fails, try submitting a URL containing a nonexistent IP
address, and determine whether a timeout occurs while the server
attempts to connect.
■
If the application is found to be vulnerable to remote file inclusion, con-
struct a malicious script using the available APIs in the relevant lan-
guage, as described for dynamic execution attacks.
Local file inclusion vulnerabilities can potentially exist in a much wider range
of scripting environments than those that support remote file inclusion. To test
for local file inclusion vulnerabilities, perform the following steps:
■
Submit the name of a known executable resource on the server, and
determine whether there is any change in the application’s behavior.
■
Do'stlaringiz bilan baham: |