CVE-2017-16212: Directory Traversal in ltt

ltt Updated 02 Oct 2025

Summary

23/07/2018
No i
High
7.5

CVE-2017-16212: Directory Traversal in ltt. Affects ltt versions < 1.1.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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The ltt package is an npm package used for local development. It provides functionality for resolving file paths. However, versions of ltt prior to 1.1.0 are vulnerable to a directory traversal attack. This vulnerability allows a malicious actor 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 ltt arises from its 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 manipulated file path to retrieve sensitive files, such as /etc/passwd. This vulnerability poses a significant risk as it can lead to the exposure of private information and 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, the best workaround is to avoid using the ltt package in production environments. Instead, consider using an alternative package that provides similar functionality but does not have the directory traversal vulnerability.

Conclusion

The ltt package has 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 information. It is recommended to avoid using ltt in production environments and switch to a different package if the functionality is required. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for ltt →

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.

Versions of ltt prior to 1.1.0 are affected by this vulnerability.

No, there is no patch available for this vulnerability.

Yes, this vulnerability can be exploited remotely by sending a manipulated file path in a GET request.

If you are using ltt for local development, it is recommended to switch to a different package. If ltt is required for production, consider using a different package that does not have this vulnerability.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

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