LFI in path
This test appends vulnerable payloads to the end of the URL, checking for Local File Inclusion vulnerabilities by manipulating file path references.
Local File Inclusion (LFI)
How this template works
The template extracts the "url" from the request and stores it in the "urlVar" variable. It also checks if the response payload contains either "<!doctype html>". These filters help in selecting the appropriate API for testing.
The template modifies the URL by removing any trailing slashes and appending "/etc/passwd" to it. This is done using the "modify_url" action. The modified request is then executed.
The template validates the response payload by checking if it matches the regex pattern "root:.*:0:0:". If the pattern is found, it indicates a successful exploitation of the Local File Inclusion vulnerability. That's it! These three steps help in identifying and exploiting Local File Inclusion vulnerabilities in a web application.
Frequently asked questions
What is the purpose of the LFI in path test
How does the LFI in path test work
What is the impact of successful exploitation of LFI in path vulnerabilities
What are the categories and subcategories associated with the LFI in path test
What are the severity and tags associated with the LFI in path test
Are there any references available for further information on the LFI in path test