# GHSA-28xh-wpgr-7fm8: Command Injection in open


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Jun 2019

## What is GHSA-28xh-wpgr-7fm8?

GHSA-28xh-wpgr-7fm8 is a vulnerability in open, published on 20 Jun 2019. 

### Official description

Versions of `open` before 6.0.0 are vulnerable to command injection when unsanitized user input is passed in.

The package does come with the following warning in the readme:

```
The same care should be taken when calling open as if you were calling child_process.exec directly. If it is an executable it will run in a new shell.
```

## Recommendation

`open` is now the deprecated `opn` package. Upgrading to the latest version is likely have unwanted effects since it now has a very different API but will prevent this vulnerability.

## Which versions are affected by GHSA-28xh-wpgr-7fm8?

2 open source packages ship an affected version, including open.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `open` | npm | All versions | 6.0.0 |
| `open` | npm | All versions | 6.0.0 |

## How do I fix GHSA-28xh-wpgr-7fm8?

Upgrade open to 6.0.0 or later.

## Is GHSA-28xh-wpgr-7fm8 being exploited?

There is no known exploitation of GHSA-28xh-wpgr-7fm8 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-28xh-wpgr-7fm8 and fix it if it is affected.

What it is: GHSA-28xh-wpgr-7fm8 is a vulnerability in open, published on 20 Jun 2019. 
Exploitation: There is no known exploitation of GHSA-28xh-wpgr-7fm8 in the wild and no public exploit code.

Affected packages and fixed versions:
- open (npm): affected all versions; fixed in 6.0.0
- open (npm): affected all versions; fixed in 6.0.0

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-28xh-wpgr-7fm8/ (Markdown: https://insights.sbomify.com/GHSA-28xh-wpgr-7fm8/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-28xh-wpgr-7fm8

---
From sbomify Insights: https://insights.sbomify.com/GHSA-28xh-wpgr-7fm8/
Summaries are generated and may contain mistakes; the official description above is the record.