Hidden functionality vulnerability in node-ipc

node-ipc Updated 02 Oct 2025

Summary

16/03/2022
LOW
No i
Low
Not published

GHSA-8gr3-2gjw-jj7g: Hidden functionality in node-ipc. Affects node-ipc versions 9.2.2. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The node-ipc package is a popular npm package used for inter-process communication in Node.js applications. It provides a simple and convenient way to communicate between different processes running on the same machine. The package version 9.2.2 has been found to have a hidden functionality vulnerability introduced by the maintainer. This vulnerability is not present in versions prior to 9.2.2. The package includes a dependency that writes a file to disk, which is unrelated to the intended functionality of the package.

Vulnerability Detail

The hidden functionality vulnerability in node-ipc can have various implications. It introduces an unexpected behavior that can potentially compromise the security and integrity of the application. The unauthorized file writing can lead to unauthorized access, data leakage, or even remote code execution. This vulnerability is classified as low severity according to the Common Weakness Enumeration (CWE) ID 912.

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

If updating the package is not immediately feasible, a temporary workaround can be implemented by manually removing the dependency that writes the unauthorized file. This can be done by modifying the package's dependencies in the package.json file and removing the specific dependency causing the issue. However, this workaround is not recommended as it may introduce other compatibility or functionality issues.

Conclusion

The hidden functionality vulnerability in node-ipc can have serious implications for the security and integrity of the application. It is recommended to update the package to a version higher than 9.2.2 to fix this vulnerability. If immediate update is not possible, a temporary workaround can be implemented by manually removing the specific dependency causing the issue. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for node-ipc →

Share this vulnerability

FAQ

Node-ipc is an npm package used for inter-process communication in Node.js applications. It provides a simple and convenient way to communicate between different processes running on the same machine.

The hidden functionality vulnerability in node-ipc can lead to unauthorized access, data leakage, or remote code execution. It compromises the security and integrity of the application.

To fix this vulnerability, update the node-ipc package to a version higher than 9.2.2. The maintainer has addressed this issue in subsequent releases.

A temporary workaround is to manually remove the dependency causing the issue from the package's dependencies in the package.json file. However, this workaround is not recommended as it may introduce other compatibility or functionality issues.

This vulnerability is classified as low severity according to the Common Weakness Enumeration (CWE) ID 912.

Related vulnerabilities

Recent vulnerabilities recorded for node-ipc.

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