CVE-2017-16215: Directory Traversal in sgqserve

sgqserve Updated 02 Oct 2025

Summary

01/09/2020
No i
High
7.5

CVE-2017-16215: Directory Traversal in sgqserve. Affects sgqserve 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 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

The sgqserve package is an npm package used for local development. It provides functionality for serving files and directories over HTTP. The package is vulnerable to a directory traversal vulnerability, 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 sgqserve arises from the package's resolution of relative file paths. By manipulating the file path in a specific way, a malicious actor 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 to retrieve sensitive files, such as /etc/passwd. This vulnerability has a high severity rating and is classified under CWE-22.

Affected versions of sgqserve include all versions starting from 0.0.0.

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

Conclusion

The sgqserve package is vulnerable to a directory traversal vulnerability that allows an attacker to access files outside of the intended directory root. This can lead to the disclosure of sensitive files on the vulnerable system. Unfortunately, there is no patch available for this vulnerability. It is advised to only use sgqserve for local development and to switch to a different package for production environments. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for sgqserve →

Share this vulnerability

FAQ

The impact of this vulnerability is the potential disclosure of private files on the vulnerable system. An attacker can access sensitive files outside of the intended directory root, which can lead to further exploitation or unauthorized access.

No, there is no patch available for this vulnerability at the moment.

Yes, this vulnerability can be exploited remotely by sending crafted requests to the affected server.

Yes, all versions of sgqserve starting from 0.0.0 are affected by this vulnerability.

If you are using sgqserve, it is recommended to only use it for local development purposes. If you require similar functionality for production, consider using a different package that does not have this vulnerability.

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