Directus affected by VM2 sandbox escape vulnerability

published 2023-09-15 3y ago modified 2023-09-15 3y ago

cvss: 7.6; 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 In vm2 for versions up to 3.9.19, Promise handler sanitization can be bypassed, allowing attackers to escape the sandbox and run arbitrary code. Within Directus this applies to the "Run Script" operation in flows being able to escape the sandbox running code in the main nodejs context.

### Patches Patched in v10.6.0 by replacing `vm2` with `isolated-vm`

### Workarounds None

### References https://github.com/patriksimek/vm2/security/advisories/GHSA-cchq-frgv-rjh5

Patch / fix

fixed in 1 links 2

npm directus 10.6.0

github.com/directus/directus@2841564 commit
github.com/directus/directus#19332 pull request

Is GHSA-22rr-f3p8-5gf8 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	7.6	CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
npm	directus	<10.6.0	10.6.0

References

Sources

GitHub Advisory GHSA-22rr-f3p8-5gf8

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.