CVE-2017-16153: Directory Traversal in gaoxuyan

gaoxuyan Updated 02 Oct 2025

Summary

01/09/2020
No i
High
7.5

CVE-2017-16153: Directory Traversal in gaoxuyan. Affects gaoxuyan 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The gaoxuyan 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, which allows a malicious actor 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 gaoxuyan arises from its improper resolution of relative file paths. By exploiting this vulnerability, an attacker can craft a request that includes a path traversal sequence, such as "../", to access files outside of the intended directory. For example, an attacker could send a GET request to access the /etc/passwd file on the system. This can result in the exposure of sensitive 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 validate and sanitize user input when resolving file paths. This can help prevent directory traversal attacks. Here is an example in JavaScript:

function resolveFilePath(userInput) {
  // Validate and sanitize userInput
  // ... your code here ...

  // Resolve the file path
  const resolvedPath = path.resolve(__dirname, userInput);

  // ... rest of your code ...
}

Conclusion

The gaoxuyan package is vulnerable to a directory traversal attack, allowing an attacker to access files outside of the intended directory root. There is no patch available for this vulnerability, so it is recommended to use the package only for local development and switch to a different package for production. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for gaoxuyan →

Share this vulnerability

FAQ

The impact of this vulnerability is that an attacker can 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 the gaoxuyan package.

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

One possible mitigation is to validate and sanitize user input when resolving file paths. Additionally, it is recommended to use a different package for production that does not have this vulnerability.

Yes, a public advisory is available for this vulnerability. You can find more information in the GitHub Advisory Database.

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