# GHSA-wgw3-gf4p-62xc: Command Injection in wizard-syncronizer

> Attackers can execute arbitrary commands via malicious widget inputs or MITM attacks in the wizard-syncronizer npm package.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Sep 2020

## What is GHSA-wgw3-gf4p-62xc?

GHSA-wgw3-gf4p-62xc is a command injection vulnerability in wizard-syncronizer, published on 11 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

All versions of `wizard-syncronizer` are vulnerable to Command Injection. The package does not validate input on the `cloneAndSync` function  and concatenates it to an exec call. This can be abused through a malicious widget containing the payload in the `gitURL` value or through a MITM attack since the package does not enforce HTTPS. This may allow attackers to run arbitrary commands in the system.

## Recommendation

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

## Which versions are affected by GHSA-wgw3-gf4p-62xc?

2 open source packages ship an affected version, including wizard-syncronizer.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wizard-syncronizer` | npm | From 0.0.0 | None |
| `wizard-syncronizer` | npm | From 0.0.0 | None |

## How do I fix GHSA-wgw3-gf4p-62xc?

No fix has been published for GHSA-wgw3-gf4p-62xc yet. Limit exposure of the affected software until one is available.

## Is GHSA-wgw3-gf4p-62xc being exploited?

There is no known exploitation of GHSA-wgw3-gf4p-62xc in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-wgw3-gf4p-62xc and fix it if it is affected.

What it is: GHSA-wgw3-gf4p-62xc is a command injection vulnerability in wizard-syncronizer, published on 11 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-wgw3-gf4p-62xc in the wild and no public exploit code.

Affected packages and fixed versions:
- wizard-syncronizer (npm): affected from 0.0.0; no fix listed
- wizard-syncronizer (npm): affected from 0.0.0; no fix listed

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-wgw3-gf4p-62xc/ (Markdown: https://insights.sbomify.com/GHSA-wgw3-gf4p-62xc/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-wgw3-gf4p-62xc

---
From sbomify Insights: https://insights.sbomify.com/GHSA-wgw3-gf4p-62xc/
Summaries are generated and may contain mistakes; the official description above is the record.