How severe is GHSA-3mpp-xfvh-qh37?

No CVSS score has been assigned to GHSA-3mpp-xfvh-qh37 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3mpp-xfvh-qh37?

GHSA-3mpp-xfvh-qh37 affects the following packages: node-ipc (npm). Ecosystems affected: npm.

How do I fix GHSA-3mpp-xfvh-qh37?

Update node-ipc to 12.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3mpp-xfvh-qh37 is resolved across your whole dependency graph.

How do I detect GHSA-3mpp-xfvh-qh37 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for node-ipc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-3mpp-xfvh-qh37 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-3mpp-xfvh-qh37?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3mpp-xfvh-qh37 can be triaged on real exposure rather than presence alone.

Is GHSA-3mpp-xfvh-qh37 actively exploited in the wild?

No public exploit code has been indexed for GHSA-3mpp-xfvh-qh37 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-3mpp-xfvh-qh37 published, and has it been updated?

GHSA-3mpp-xfvh-qh37 was published on March 16, 2022 and was last updated on August 14, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-3mpp-xfvh-qh37 — node-ipc

Fix: RIAEvangelist/node-ipc@a98efae

GHSA-3mpp-xfvh-qh37 is a security vulnerability in node-ipc. A fix is available for node-ipc — see the affected versions and patch details below.

node-ipc behavior change

Published

Mar 16, 2022

Updated

Aug 14, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 14, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

427other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

node-ipcnpm

703Kdownloads / week

Description

node-ipc starting in version 11.0.0 and prior to version 12.0.0 includes a message from the maintainer that is written to the user’s desktop. Please review the version changes before proceeding.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`node-ipc`	≥ 11.0.0&&< 12.0.0	12.0.0`npm install node-ipc@12.0.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for node-ipc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update node-ipc to 12.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3mpp-xfvh-qh37 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3mpp-xfvh-qh37 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-3mpp-xfvh-qh37. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

node-ipc starting in version 11.0.0 and prior to version 12.0.0 includes a message from the maintainer that is written to the user’s desktop. Please review the version changes before proceeding.

O3 Security · Impact-Aware SCA

Is GHSA-3mpp-xfvh-qh37 in your dependencies?

O3 Security finds GHSA-3mpp-xfvh-qh37 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works