CVE-2017-16089: Directory Traversal in serverlyr

serverlyr Updated 02 Oct 2025

Summary

01/09/2020
No i
High
7.5

CVE-2017-16089: Directory Traversal in serverlyr. Affects serverlyr 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 serverlyr package is an npm module used for server-side development. It provides functionality for handling server requests and responses. However, this package is vulnerable to a directory traversal attack, which allows an attacker to access files outside of the intended directory root. This can lead to the disclosure of sensitive files on the affected system.

Vulnerability Detail

The vulnerability in serverlyr 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 that should be inaccessible. For example, an attacker can send a crafted HTTP request with a relative file path that goes beyond the intended directory root, such as GET /../../../etc/passwd. This would allow the attacker to retrieve the /etc/passwd file, which may contain sensitive information like user credentials.

This vulnerability has a high severity rating and is classified under CWE-22 (Path Traversal).

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 serverlyr in production environments. Instead, consider using an alternative package that provides similar functionality but does not suffer from the directory traversal vulnerability.

Conclusion

The serverlyr package is vulnerable to a directory traversal attack, which can lead to the disclosure of sensitive files. Unfortunately, no patch is available for this vulnerability. It is advised to use serverlyr only for local development and switch to a different package for production. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for serverlyr →

Share this vulnerability

FAQ

The impact of this vulnerability is the potential disclosure of sensitive files on the affected system. An attacker can access files outside of the intended directory root, which may include private files containing sensitive information.

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

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

This vulnerability has a high severity rating.

If you are using serverlyr, it is recommended to only use it for local development purposes. For production environments, switch to a different package that does not have this 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