# GHSA-4x6x-782q-jfc4: Command Injection in node-wifi

> Attackers can inject commands via the ssid variable in node-wifi, potentially achieving remote code execution on the host system.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2020

## What is GHSA-4x6x-782q-jfc4?

GHSA-4x6x-782q-jfc4 is a command injection vulnerability in node-wifi, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Versions of `node-wifi` prior to 2.0.12 are vulnerable to Command Injection. The package fails to sanitize user input, allowing attackers to inject commands through the `ssid` variable and possibly achieving Remote Code Execution on the system.

## Recommendation

No fix is currently available. Consider using an alternative package until a fix is made available.

## Which versions are affected by GHSA-4x6x-782q-jfc4?

2 open source packages ship an affected version, including node-wifi.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node-wifi` | npm | All versions | 2.0.12 |
| `node-wifi` | npm | All versions | 2.0.12 |

## How do I fix GHSA-4x6x-782q-jfc4?

Upgrade node-wifi to 2.0.12 or later.

## Is GHSA-4x6x-782q-jfc4 being exploited?

There is no known exploitation of GHSA-4x6x-782q-jfc4 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-4x6x-782q-jfc4 and fix it if it is affected.

What it is: GHSA-4x6x-782q-jfc4 is a command injection vulnerability in node-wifi, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-4x6x-782q-jfc4 in the wild and no public exploit code.

Affected packages and fixed versions:
- node-wifi (npm): affected all versions; fixed in 2.0.12
- node-wifi (npm): affected all versions; fixed in 2.0.12

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-4x6x-782q-jfc4/ (Markdown: https://insights.sbomify.com/GHSA-4x6x-782q-jfc4/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-4x6x-782q-jfc4

---
From sbomify Insights: https://insights.sbomify.com/GHSA-4x6x-782q-jfc4/
Summaries are generated and may contain mistakes; the official description above is the record.