CVE-2017-16188: Directory Traversal in reecerver

reecerver Updated 02 Oct 2025

Summary

23/07/2018
No i
High
7.5

CVE-2017-16188: Directory Traversal in reecerver. Affects reecerver versions < 0.1.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

reecerver is an npm package used for local development. It provides functionality for resolving relative file paths. However, it is vulnerable to a directory traversal attack, where a malicious actor can 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 reecerver arises from its improper resolution of relative file paths. By exploiting this vulnerability, an attacker can craft requests that traverse directories and access files outside of the intended directory root. For example, an attacker can send a GET request with a crafted path to access sensitive files like '/etc/passwd'. This can result in the unauthorized disclosure of private information.

How To Fix

No fixed version is published for this vulnerability.

Unfortunately, there is no patch available for this vulnerability in reecerver. It is recommended to only use this package for local development purposes. If the functionality provided by reecerver is required for production, it is advised to switch to a different package that does not have 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 avoid using reecerver in production environments. Instead, consider using an alternative package that provides similar functionality but does not suffer from the directory traversal vulnerability.

Conclusion

In conclusion, reecerver is vulnerable to a directory traversal attack, allowing an attacker to access files outside of the intended directory root. No patch is available, so it is advised to use reecerver only for local development and switch to a different package for production. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for reecerver →

Share this vulnerability

FAQ

reecerver is an npm package used for local development. It helps resolve relative file paths.

Directory traversal is a vulnerability that allows an attacker to access files outside of the intended directory root by manipulating file paths.

By exploiting directory traversal, an attacker can access sensitive files, such as configuration files or user data, that are stored outside of the intended directory root.

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

To mitigate the risk, it is recommended to only use reecerver for local development and switch to a different package for production environments.

How To Fix

No fixed version is published for this vulnerability.

Unfortunately, there is no patch available for this vulnerability in reecerver. It is recommended to only use this package for local development purposes. If the functionality provided by reecerver is required for production, it is advised to switch to a different package that does not have 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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.