Absolute Path Traversal due to incorrect use of send_file call
A path traversal attack (also known as directory traversal) aims to access files and directories that are stored outside the web root folder. By manipulating variables that reference files with “dot-dot-slash (../)” sequences and its variations or by using absolute file paths, it may be possible to access arbitrary files and directories stored on file system including application source code or configuration and critical system files. This attack is also known as “dot-dot-slash”, “directory traversal”, “directory climbing” and “backtracking”.
Root Cause Analysis
The os.path.join call is unsafe for use with untrusted input. When the os.path.join call encounters an absolute path, it ignores all the parameters it has encountered till that point and starts working with the new absolute path. Please see the example below.
Since the "malicious" parameter represents an absolute path, the result of os.path.join ignores the static directory completely. Hence, untrusted input is passed via the os.path.join call to flask.send_file can lead to path traversal attacks.
Here, the ` parameter is attacker controlled. This parameter passes through the unsafeos.path.joincall making the effective directory and filename passed to thesend_file` call attacker controlled. This leads to a path traversal attack.
Remediation
This can be fixed by preventing flow of untrusted data to the vulnerable send_file function. In case the application logic necessiates this behaviour, one can either use the flask.safe_join to join untrusted paths or replace flask.send_file calls with flask.send_from_directory calls.
Absolute Path Traversal due to incorrect use of
send_filecallA path traversal attack (also known as directory traversal) aims to access files and directories that are stored outside the web root folder. By manipulating variables that reference files with “dot-dot-slash (../)” sequences and its variations or by using absolute file paths, it may be possible to access arbitrary files and directories stored on file system including application source code or configuration and critical system files. This attack is also known as “dot-dot-slash”, “directory traversal”, “directory climbing” and “backtracking”.
Root Cause Analysis
The
os.path.joincall is unsafe for use with untrusted input. When theos.path.joincall encounters an absolute path, it ignores all the parameters it has encountered till that point and starts working with the new absolute path. Please see the example below.Since the "malicious" parameter represents an absolute path, the result of
os.path.joinignores the static directory completely. Hence, untrusted input is passed via theos.path.joincall toflask.send_filecan lead to path traversal attacks.In this case, the problems occurs due to the following code : https://github.com/ChaoticOnyx/OnyxForum/blob/4077b499a1ca213f3eb55b8321a4733d83531750/modules/hub/hub/views.py#L493
Here, the
` parameter is attacker controlled. This parameter passes through the unsafeos.path.joincall making the effective directory and filename passed to thesend_file` call attacker controlled. This leads to a path traversal attack.Remediation
This can be fixed by preventing flow of untrusted data to the vulnerable
send_filefunction. In case the application logic necessiates this behaviour, one can either use theflask.safe_jointo join untrusted paths or replaceflask.send_filecalls withflask.send_from_directorycalls.References
This bug was found using CodeQL by Github