# GHSA-g6w6-h933-4rc5: Soketi was exposed to Sandbox Escape vulnerability via vm2

> Soketi users using the cluster driver or PM2 are vulnerable to sandbox escape via vm2, allowing arbitrary code execution.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Aug 2023

## What is GHSA-g6w6-h933-4rc5?

GHSA-g6w6-h933-4rc5 is a code injection vulnerability in @soketi/soketi, published on 3 Aug 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

### Impact
_What kind of vulnerability is it? Who is impacted?_
Anyone who might have used Soketi with the `cluster` driver (or through PM2).

### Patches
_Has the problem been patched? What versions should users upgrade to?_
Get the latest version of Soketi.

### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
None. It's advised to upgrade to the latest version.

### References
_Are there any links users can visit to find out more?_
- https://github.com/advisories/GHSA-cchq-frgv-rjh5
- https://github.com/patriksimek/vm2/issues/533
- https://github.com/Unitech/pm2/issues/5643

## Which versions are affected by GHSA-g6w6-h933-4rc5?

2 open source packages ship an affected version, including @soketi/soketi.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@soketi/soketi` | npm | All versions | 1.6.0 |
| `@soketi/soketi` | npm | All versions | 1.6.0 |

## How do I fix GHSA-g6w6-h933-4rc5?

Upgrade @soketi/soketi to 1.6.0 or later.

## Is GHSA-g6w6-h933-4rc5 being exploited?

There is no known exploitation of GHSA-g6w6-h933-4rc5 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-g6w6-h933-4rc5 and fix it if it is affected.

What it is: GHSA-g6w6-h933-4rc5 is a code injection vulnerability in @soketi/soketi, published on 3 Aug 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-g6w6-h933-4rc5 in the wild and no public exploit code.

Affected packages and fixed versions:
- @soketi/soketi (npm): affected all versions; fixed in 1.6.0
- @soketi/soketi (npm): affected all versions; fixed in 1.6.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-g6w6-h933-4rc5/ (Markdown: https://insights.sbomify.com/GHSA-g6w6-h933-4rc5/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-g6w6-h933-4rc5

---
From sbomify Insights: https://insights.sbomify.com/GHSA-g6w6-h933-4rc5/
Summaries are generated and may contain mistakes; the official description above is the record.