Arbitrary File Write via Archive Extraction (Zip Slip) Affecting github.com/codeclysm/extract package, versions *


Severity

Recommended
0.0
medium
0
10

CVSS assessment made by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.04% (13th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-GOLANG-GITHUBCOMCODECLYSMEXTRACT-8184982
  • published13 Oct 2024
  • disclosed11 Oct 2024
  • creditbuglloc

Introduced: 11 Oct 2024

CVE-2024-47877  (opens in a new tab)
CWE-29  (opens in a new tab)
CWE-61  (opens in a new tab)

How to fix?

There is no fixed version for github.com/codeclysm/extract.

Overview

github.com/codeclysm/extract is a Package that allows to extract archives in zip, tar.gz or tar.bz2 formats easily.

Affected versions of this package are vulnerable to Arbitrary File Write via Archive Extraction (Zip Slip) due to improper input validation in the ‎extractor.go component. By crafting a malicious archive, an attacker can create symlinks that point to arbitrary locations outside the intended extraction directory.

Note:

This vulnerability was fixed in v4, all other versions are affected.

Details

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:


+2018-04-15 22:04:29 ..... 19 19 good.txt

+2018-04-15 22:04:42 ..... 20 20 ../../../../../../root/.ssh/authorized_keys

References

CVSS Scores

version 4.0
version 3.1