File Inclusion

http://localhost/DVWA/vulnerabilities/fi

What is a File Inclusion?

A file inclusion attack is a type of security exploit that takes advantage of improper or unchecked input handling in web applications. The goal of such an attack is to include files on a server through the web browser. There are two main types of file inclusion attacks: Local File Inclusion (LFI) and Remote File Inclusion (RFI).

  1. Local File Inclusion (LFI):

    • In an LFI attack, an attacker tries to include files that are already present on the target system. These files could be configuration files, system files, or any other sensitive information.

    • The attacker manipulates input parameters or user-controlled data in a way that the application includes a file from the local file system.

    • For example, if a web application includes a file based on user input without proper validation, an attacker might input a malicious path to include sensitive files.

  2. Remote File Inclusion (RFI):

    • RFI is a more severe form of file inclusion attack where the attacker includes files from a remote server controlled by them.

    • The attacker injects a URL pointing to a file on a remote server into a parameter or input field, and the application fetches and includes the contents of that remote file.

    • This can lead to the execution of arbitrary code on the server, potentially allowing the attacker to take control of the system.

File inclusion vulnerabilities can occur due to poor input validation and lack of proper security measures in web applications. To prevent file inclusion attacks, developers should:

  • Validate and sanitize user input.

  • Avoid dynamically including files based on user input without proper validation.

  • Implement proper access controls to restrict file access.

  • Use secure coding practices and frameworks that handle user input securely.

Regular security assessments, code reviews, and penetration testing can help identify and mitigate file inclusion vulnerabilities in web applications.

Using BurpSuite and the FoxyProxy extension is recommended.

Low

We've a div containing three distinct hyperlinks, each triggering the display of various files within the web application upon activation. The exhibition of a specific file is accomplished through the utilization of the subsequent GET request.

file1.pho
file2.php
file3.php

This is php code of this level:

The concept involves manipulating the filename within the page parameter to any desired file on the target, enabling us to retrieve its contents. By employing the following GET request, we can read the contents of the etc password file.

1st Payload

Replacing this path: ../../../../../../etc/passwd at file1.php, we obtain result of command in html output:

If the goal is to disclose certain PHP code, one approach is to utilize PHP filters to encode the PHP code into base64.

2nd Payload

but the request is to see fi.php file, then we use this URL:

which gives us the following base64 payload

Decoding it, we obtain this php code:

The input is not sanitized, so I can execute any (potentially malicious) command.

Medium

In this case, code includes a little validation checks:

$file = str_replace( array( "http://", "https://" ), "", $file ); $file = str_replace( array( "../", "..\\" ), "", $file );

it tries to remove all sorts of http and https protocol usage, trying to remove the possibility for a Remote File Inclusion (RFI), and it also replaces ../ with the empty string: "".

The handling of the '../' character sequence is insufficient, as the validation is not performed recursively.

1st Payload

After input validation (not recursive), changing ../ to "", we obtain this result:

Then full URL will be this:

How the low level, adding the php filters we can also leak the server’s php code:

and we get the following base64

To get an RFI instead we can use php streams.

The input is not sanitized sufficiently , so I can execute any (potentially malicious) command.

High

In this code the're two validation checks:

  1. The fnmatch() function in PHP, which matches strings against patterns using shell-style wildcards. In our scenario, it matches any file that begins with 'file.'

  2. The condition $file != 'include.php' introduces a specific case where the 'if' statement fails only when the file doesn't start with 'file' and is precisely 'include.php'.

1st Payload

Regarding LFI exploitation, the code solely verifies whether the parameter begins with 'file' and does not examine its ending. Consequently, we can employ the following GET request to expose the 'passwd' file.

however we cannot seem to able to use the php filters to leak php code by using the base64 converter.

2nd Payload

An alternative approach involves leveraging the file protocol to access and read any file in the system based on its given path.

The input is not sanitized sufficiently , so I can execute any (potentially malicious) command.

Impossible

Site isn't vulnerable to File Inclusion attack because the request includes only possible lecit value/page.

References

For the making of this solution the following resource were used:

PreviousCSRFNextFile Upload --