Arbitrary File Write via Archive Extraction (Zip Slip) Affecting github.com/nats-io/nats-server/server package, versions >=2.2.0 <2.7.4


0.0
high

Snyk CVSS

    Attack Complexity Low
    Confidentiality High

    Threat Intelligence

    EPSS 0.08% (34th percentile)
Expand this section
NVD
6.5 medium

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 ID SNYK-GOLANG-GITHUBCOMNATSIONATSSERVERSERVER-2421210
  • published 11 Mar 2022
  • disclosed 11 Mar 2022
  • credit Yiming Xiang, TIANJI LAB of NSFOCUS

How to fix?

Upgrade github.com/nats-io/nats-server/server to version 2.7.4 or higher.

Overview

github.com/nats-io/nats-server/server is an A simple, secure and performant communications system for digital systems, services and devices.

Affected versions of this package are vulnerable to Arbitrary File Write via Archive Extraction (Zip Slip) in the stream restore. This due to inadequate checks on the filenames within the archive file which can lead to a path traversal.

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