Directory Traversal Affecting git/git package, versions [,2.30.9)[2.31.0,2.31.8)[2.32.0,2.32.7)[2.33.0,2.33.8)[2.34.0,2.34.8)[2.35.0,2.35.8)[2.36.0,2.36.6)[2.37.0,2.37.7)[2.38.0,2.38.5)[2.39.0,2.39.3)[2.40.0,2.40.1)

Affected versions of this package are vulnerable to Directory Traversal where a path outside the working tree can be overwritten with partially controlled contents corresponding to the rejected hunks from the given patch.

1. Avoid using git apply with --reject when applying patches from an untrusted source.

2. Use git apply --stat to inspect a patch before applying.

3. Avoid applying one that create a conflict where a link corresponding to the *.rej file exists.

A Directory Traversal attack (also known as path traversal) aims to access files and directories that are stored outside the intended folder. By manipulating 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, configuration, and other critical system files.

Directory Traversal vulnerabilities can be generally divided into two types:

• Information Disclosure: Allows the attacker to gain information about the folder structure or read the contents of sensitive files on the system.

st is a module for serving static files on web pages, and contains a vulnerability of this type. In our example, we will serve files from the public route.

If an attacker requests the following URL from our server, it will in turn leak the sensitive private key of the root user.

curl http://localhost:8080/public/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/root/.ssh/id_rsa

Note %2e is the URL encoded version of . (dot).

• Writing arbitrary files: Allows the attacker to create or replace existing files. This type of vulnerability is also known as Zip-Slip.

One way to achieve this is by using a malicious zip archive that holds path traversal filenames. When each filename in the zip archive gets concatenated to the target extraction folder, without validation, the final path ends up outside of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily.

The following is an example of a zip archive with one benign file and one malicious file. Extracting the malicious file will result in traversing out of the target folder, ending up in /root/.ssh/ overwriting the authorized_keys file:

2018-04-15 22:04:29 .....           19           19  good.txt
2018-04-15 22:04:42 .....           20           20  ../../../../../../root/.ssh/authorized_keys

• GitHub Commit
• GitHub Commit