CVE-2017-16095: Directory Traversal in serverliujiayi1

serverliujiayi1 Updated 02 Oct 2025

Summary

01/09/2020
No i
High
7.5

CVE-2017-16095: Directory Traversal in serverliujiayi1. Affects serverliujiayi1 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 serverliujiayi1 package is an npm package used for local development. It provides functionality for resolving relative file paths. However, it is vulnerable to a directory traversal vulnerability, which 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 serverliujiayi1 arises from its improper resolution of relative file paths. By exploiting this vulnerability, an attacker can craft a malicious request to access files outside of the intended directory root. For example, an attacker can use a GET request with a crafted path to access sensitive files such as /etc/passwd. This can result in the unauthorized disclosure of private information.

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, a possible workaround is to manually sanitize and validate user input to prevent directory traversal attacks. This can be done by ensuring that user-supplied file paths are restricted to the intended directory root and do not contain any relative path components.

Conclusion

The serverliujiayi1 package is vulnerable to a directory traversal vulnerability, which allows attackers to access sensitive files outside of the intended directory root. No patch is available for this vulnerability, and it is recommended to use this package only for local development purposes. If the functionality is needed for production, it is advisable to switch to a different package. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for serverliujiayi1 →

Share this vulnerability

FAQ

The vulnerability allows attackers to access sensitive files outside of the intended directory root, potentially leading to the disclosure of private information.

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

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

One possible mitigation is to restrict the usage of serverliujiayi1 to local development only and switch to a different package for production environments.

Yes, Vulert is an active monitoring and alerting service that can help identify and track open-source vulnerabilities, including this vulnerability in serverliujiayi1.

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