CVE-2017-16169: Directory Traversal in looppake

looppake Updated 02 Oct 2025

Summary

23/07/2018
No i
High
Not published

CVE-2017-16169: Directory Traversal in looppake. Affects looppake versions < 3.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 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

looppake is an npm package used for local development. It provides functionality for resolving file paths. However, versions of looppake prior to 3.0.0 are vulnerable to a directory traversal attack. This vulnerability allows an attacker to access files outside of the intended directory root, potentially leading to the disclosure of sensitive information on the affected system.

Vulnerability Detail

The vulnerability in looppake 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 scope. For example, an attacker could send a GET request with a crafted file path to retrieve sensitive files, such as /etc/passwd. This vulnerability poses a high risk as it can lead to the exposure of private files and potentially compromise the security of the system.

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 avoid using the looppake package in production environments. Instead, consider using an alternative package that does not suffer from the directory traversal vulnerability.

Conclusion

looppake versions prior to 3.0.0 are vulnerable to a directory traversal attack. It is recommended to avoid using this package in production environments and switch to an alternative package that does not have this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for looppake →

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 on the affected system.

No, there is no patch available for this vulnerability.

Yes, looppake can still be used for local development as long as the vulnerability is not exploited. However, it is recommended to switch to a different package for production environments.

Yes, there are alternative packages available that provide similar functionality without the directory traversal vulnerability. It is recommended to explore these alternatives for production use.

You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation.

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