Arbitrary File Write via Archive Extraction (Zip Slip)
Vulnerable module:
unzipper
Introduced through:
unzipper@0.6.0
Detailed paths
Introduced through:
unzipper@0.6.0
Remediation:
Upgrade to unzipper@0.8.13.
Overview
unzipper is a library for the Uzip cross-platform streaming AP.I
Affected versions of this package are vulnerable to Arbitrary File Write via Archive Extraction (Zip Slip).
Overview
unzipper is an Unzip cross-platform streaming API.
Affected versions of the package are vulnerable to Arbitrary File Write via Archive Extraction (AKA "Zip Slip").
It is exploited using a specially crafted zip archive, that holds path traversal filenames. When exploited, a filename in a malicious archive is concatenated to the target extraction directory, which results in the final path ending up outside of the target folder. For instance, a zip may hold a file with a "../../file.exe" location and thus break out 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 malicous file will result in traversing out of the target folder, ending up in /root/.ssh/ overwriting the authorized_keys file:
It is exploited using a specially crafted zip archive, that holds path traversal filenames. When exploited, a filename in a malicious archive is concatenated to the target extraction directory, which results in the final path ending up outside of the target folder. For instance, a zip may hold a file with a "../../file.exe" location and thus break out 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 malicous file will result in traversing out of the target folder, ending up in /root/.ssh/ overwriting the authorized_keys file: