CVE-2017-16135: Directory Traversal in serverzyy

serverzyy Updated 02 Oct 2025

Summary

01/09/2020
No i
High
Not published

CVE-2017-16135: Directory Traversal in serverzyy. Affects serverzyy 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The serverzyy package is an npm package used for server-side development. It provides various functionalities for building server applications. However, it is vulnerable to a directory traversal vulnerability that allows malicious actors to 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 serverzyy arises from the way it resolves relative file paths. By manipulating the file path in a specific manner, an attacker can traverse directories and access files outside of the intended directory root. This can result in the exposure of sensitive information, such as private files or configuration files. An example request that demonstrates this vulnerability is:

GET /../../../etc/passwd HTTP/1.1
host: foo

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 best workaround is to avoid using the serverzyy package in production environments. Instead, consider using an alternative package that does not have the directory traversal vulnerability.

Conclusion

The serverzyy package is vulnerable to a directory traversal vulnerability that allows unauthorized access to files outside of the intended directory root. It is recommended to avoid using this package in production environments and switch to a different package. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for serverzyy →

Share this vulnerability

FAQ

The impact of this vulnerability is the potential disclosure of private files on the vulnerable system. This can lead to unauthorized access to sensitive information and compromise the security of the system.

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

No, there is no patch available for this vulnerability in the serverzyy package.

The best mitigation for this vulnerability is to avoid using the serverzyy package in production environments and switch to a different package that does not have this vulnerability.

Yes, you can use Vulert (https://vulert.com) to monitor and receive real-time alerts for open-source vulnerabilities, including this vulnerability in the serverzyy package.

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