How severe is GHSA-w725-67p7-xv22?

No CVSS score has been assigned to GHSA-w725-67p7-xv22 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w725-67p7-xv22?

GHSA-w725-67p7-xv22 affects the following packages: local-devices (npm). Ecosystems affected: npm.

How do I fix GHSA-w725-67p7-xv22?

Update local-devices to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w725-67p7-xv22 is resolved across your whole dependency graph.

How do I detect GHSA-w725-67p7-xv22 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for local-devices. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-w725-67p7-xv22 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-w725-67p7-xv22?

O3 pinpoints whether GHSA-w725-67p7-xv22 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-w725-67p7-xv22 actively exploited in the wild?

No public exploit code has been indexed for GHSA-w725-67p7-xv22 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-w725-67p7-xv22 published, and has it been updated?

GHSA-w725-67p7-xv22 was published on September 3, 2020 and was last updated on September 28, 2021. 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-w725-67p7-xv22

Fix: DylanPiercey/local-devices#16

GHSA-w725-67p7-xv22 is a remote code execution vulnerability in local-devices. O3 Security confirms whether GHSA-w725-67p7-xv22 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Command Injection in local-devices

Published

Sep 3, 2020

Updated

Sep 28, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 28, 2021 · 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.

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

local-devicesnpm

2Kdownloads / week

Description

Versions of local-devices prior to 3.0.0 are vulnerable to Command Injection. The package does not validate input on ip addresses and concatenates it to an exec call, allowing attackers to run arbitrary commands in the system.

Recommendation

Upgrade to version 3.0.0 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`local-devices`	all versions	3.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 local-devices. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update local-devices to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w725-67p7-xv22 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 pinpoints whether GHSA-w725-67p7-xv22 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-w725-67p7-xv22. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `local-devices` prior to 3.0.0 are vulnerable to Command Injection. The package does not validate input on ip addresses and concatenates it to an exec call, allowing attackers to run arbitrary commands in the system. ## Recommendation Upgrade to version 3.0.0 or later.

O3 Security · Impact-Aware SCA

Is GHSA-w725-67p7-xv22 in your dependencies?

O3 detects GHSA-w725-67p7-xv22 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works