CVE-2017-16105: Directory Traversal in serverwzl

serverwzl Updated 02 Oct 2025

Summary

01/09/2020
No i
High
7.5

CVE-2017-16105: Directory Traversal in serverwzl. Affects serverwzl versions >= 0.0.0. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The serverwzl package is an npm package used for local development. It provides functionality for resolving file paths. However, it is vulnerable to a directory traversal attack, where a malicious actor can access files outside of the intended directory root. This can lead to the disclosure of private files on the vulnerable system.

Vulnerability Detail

The vulnerability in serverwzl arises from its resolution of relative file paths. By manipulating the file path in a specific way, an attacker can traverse directories and access files outside of the intended scope. For example, an attacker can send a GET request with a crafted file path to retrieve sensitive files, such as /etc/passwd. This vulnerability has a high severity rating and is classified under CWE-22.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As there is no patch available, the only workaround is to avoid using serverwzl in production environments. Instead, consider using an alternative package that does not have the directory traversal vulnerability.

Conclusion

The serverwzl package is vulnerable to a directory traversal attack, allowing an attacker to access files outside of the intended directory root. As there is no patch available, it is advised to only use this package for local development purposes. For production environments, it is recommended to switch to an alternative package that does not have this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for serverwzl →

Share this vulnerability

FAQ

The impact of this vulnerability is the potential disclosure of private files on the vulnerable system. An attacker can access sensitive files outside of the intended directory root, which can lead to further exploitation or unauthorized access.

No, there is no patch available for this vulnerability in serverwzl.

Yes, this vulnerability can be exploited remotely by sending crafted requests to the vulnerable server.

This vulnerability has a high severity rating.

Yes, it is recommended to switch to a different package that does not have the directory traversal vulnerability.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback