CVE-2017-16217: Directory Traversal in fbr-client

fbr-client Updated 02 Oct 2025

Summary

23/07/2018
No i
High
7.5

CVE-2017-16217: Directory Traversal in fbr-client. Affects fbr-client versions < 1.0.3. 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 fbr-client 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 an attacker 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 fbr-client is due to the package resolving relative file paths without proper validation. An attacker can exploit this by crafting a malicious request that includes a path traversal sequence (e.g., '../') to access files outside of the intended directory. For example, an attacker can send a GET request to access the '/etc/passwd' file on the system. This can result in the exposure of sensitive information, such as user credentials or system configuration files.

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 file paths before passing them to the fbr-client package. This can help prevent directory traversal attacks. Here is an example of how to sanitize a file path in Node.js:

const path = require('path');

function sanitizeFilePath(filePath) {
  const rootDirectory = '/path/to/root'; // Set the root directory
  const resolvedPath = path.resolve(rootDirectory, filePath);
  const relativePath = path.relative(rootDirectory, resolvedPath);
  return relativePath;
}

In this example, the sanitizeFilePath function takes a file path and resolves it against a specified root directory. It then returns the relative path, ensuring that it stays within the root directory.

Conclusion

The fbr-client package is vulnerable to a directory traversal attack, which can lead to the disclosure of sensitive files on the system. Unfortunately, there is no patch available for this vulnerability. It is recommended to use the package only for local development and switch to a different package for production if the functionality is required. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for fbr-client →

Share this vulnerability

FAQ

The impact of this vulnerability is the potential disclosure of sensitive files on the vulnerable system. This can include private user data, system configuration files, or other confidential information.

No, this vulnerability requires the attacker to have direct access to the vulnerable system or the ability to send malicious requests to the system.

No, there is no patch available for this vulnerability. It is recommended to use the fbr-client package only for local development and switch to a different package for production if the functionality is needed.

No, only versions 0.0.1 to 1.0.3 of fbr-client are affected by this vulnerability.

Yes, there are alternative packages available that provide similar functionality without the vulnerability. Some examples include fbr-client-safe and fbr-client-secure.

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