CVE-2017-16223: Directory Traversal in nodeaaaaa

nodeaaaaa Updated 02 Oct 2025

Summary

23/07/2018
No i
High
7.5

CVE-2017-16223: Directory Traversal in nodeaaaaa. Affects nodeaaaaa versions < 1.3.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 nodeaaaaa package is an npm package used for local development. It resolves relative file paths but is vulnerable to a directory traversal vulnerability. 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 nodeaaaaa arises from its resolution of relative file paths. By exploiting this vulnerability, an attacker can craft a request that includes file path traversal sequences, such as '../', to access files outside of the intended directory. For example, an attacker could send a GET request to access the '/etc/passwd' file on the system. This could 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 validate and sanitize user input to prevent directory traversal attacks. This can be done by ensuring that user-supplied file paths are restricted to the intended directory root and do not contain any traversal sequences.

Conclusion

The nodeaaaaa package is vulnerable to a directory traversal vulnerability that allows an attacker to access files outside of the intended directory root. While no patch is available, it is recommended to use nodeaaaaa only for local development purposes. If the functionality is required for production, consider using alternative packages without this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for nodeaaaaa →

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, it is still safe to use nodeaaaaa for local development purposes. However, caution should be exercised when using it in a production environment.

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

To prevent directory traversal attacks, always validate and sanitize user input for file paths. Ensure that user-supplied file paths are restricted to the intended directory root and do not contain any traversal sequences.

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