CVE-2017-16130: Directory Traversal in exxxxxxxxxxx

exxxxxxxxxxx Updated 02 Oct 2025

Summary

23/07/2018
No i
High
7.5

CVE-2017-16130: Directory Traversal in exxxxxxxxxxx. Affects exxxxxxxxxxx versions < 1.0.2. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

exxxxxxxxxxx is an npm package used for [provide brief description of the package functionality]. It is vulnerable to a directory traversal vulnerability, 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. The vulnerability is effective for files with a file extension, but partial mitigation is provided. The affected versions range from 0 to 1.0.2.

Vulnerability Detail

The directory traversal vulnerability in exxxxxxxxxxx arises from the package resolving relative file paths. By exploiting this vulnerability, an attacker can manipulate file paths to access files outside of the intended directory root. This can result in the unauthorized disclosure of sensitive information. An example request that demonstrates this vulnerability is:

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

The package does not have a patch available to fix this vulnerability. It is recommended to only use this package for local development. If the functionality is required for production, it is advised to use an alternative 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 →

Workaround

As there is no patch available, a workaround for this vulnerability 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 allow any relative path traversal.

Conclusion

exxxxxxxxxxx is vulnerable to a directory traversal vulnerability that allows unauthorized access to files outside of the intended directory root. No patch is available, so it is recommended to use the package only for local development. If the package is needed for production, it is advised to switch to a different package. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for exxxxxxxxxxx →

Share this vulnerability

FAQ

This vulnerability allows an attacker to access files outside of the intended directory root, potentially leading to the disclosure of sensitive information.

No, there is no patch available for this vulnerability.

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

No, only versions 0 to 1.0.2 of exxxxxxxxxxx are affected by this vulnerability.

Yes, it is recommended to use an alternative package that does not have this vulnerability if the functionality provided by exxxxxxxxxxx is required for production.

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