CVE-2017-16148: Directory Traversal in serve46

serve46 Updated 02 Oct 2025

Summary

01/09/2020
No i
High
7.5

CVE-2017-16148: Directory Traversal in serve46. Affects serve46 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The serve46 package is an npm package used for local development. It provides functionality for serving files over HTTP. However, it is vulnerable to a directory traversal vulnerability. This vulnerability allows an attacker to access files outside of the intended directory root, potentially leading to the disclosure of private files on the vulnerable system.

Vulnerability Detail

The vulnerability in serve46 arises from the package's resolution of relative file paths. By manipulating the file path in a specific way, an attacker can traverse directories and access files outside of the intended directory root. For example, an attacker can send a GET request with a crafted file path like GET /../../../etc/passwd to retrieve the /etc/passwd file. 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 implement file serving functionality in your application, ensuring that proper security measures are in place to prevent directory traversal attacks. Here is an example of how you can serve files using the express package:

const express = require('express');
const path = require('path');

const app = express();

app.get('/files/*', (req, res) => {
  const filePath = path.join(__dirname, req.params[0]);
  res.sendFile(filePath);
});

app.listen(3000, () => {
  console.log('Server is running on port 3000');
});

Conclusion

The serve46 package is vulnerable to a directory traversal vulnerability that allows an attacker to access files outside of the intended directory root. No patch is available for this vulnerability, so it is recommended to use the package only for local development purposes. If the functionality is needed for production, it is advised to use a different package or implement your own file serving functionality with proper security measures. For more information and support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for serve46 →

Share this vulnerability

FAQ

The 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, you can continue using serve46 for local development purposes. However, it is recommended to use a different package for production or implement your own file serving functionality with proper security measures.

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. It analyzes your package-lock.json file and alerts you in real-time for open-source vulnerabilities.

For further support on vulnerability remediation, you can reach out to info@devnack.com.

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