Soketi was exposed to Sandbox Escape vulnerability via vm2

published 2023-08-03 3y ago modified 2023-08-03 3y ago

cvss: 9.8; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

### 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

Patch / fix

fixed in 1 links 3

npm @soketi/soketi 1.6.0

github.com/soketi/soketi@de12bff commit
github.com/soketi/soketi#927 pull request
github.com/soketi/soketi/releases/tag/1.6.0 release

Is GHSA-g6w6-h933-4rc5 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
npm	@soketi/soketi	<1.6.0	1.6.0

References

Sources

GitHub Advisory GHSA-g6w6-h933-4rc5

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.