vm2 is a sandbox that can run untrusted code with Node's built-in modules. In versions 3.9.17 and lower of vm2 it was possible to get a read-write reference to the node `inspect` method and edit options for `console.log`. As a result a threat actor can edit options for the `console.log` command. This vulnerability was patched in the release of version `3.9.18` of `vm2`. Users are advised to upgrade. Users unable to upgrade may make the `inspect` method readonly with `vm.readonly(inspect)` after creating a vm.

Affected: npm: vm2

In versions 3.9.17 and lower of vm2 it was possible to get a read-write reference to the node `inspect` method and edit options for `console.log`.

### Impact A threat actor can edit options for `console.log`.

### Patches This vulnerability was patched in the release of version `3.9.18` of `vm2`.

### Workarounds After creating a vm make the `inspect` method readonly with `vm.readonly(inspect)`.

### References PoC - https://gist.github.com/arkark/c1c57eaf3e0a649af1a70c2b93b17550

### For more information

If you have any questions or comments about this advisory:

- Open an issue in [VM2](https://github.com/patriksimek/vm2)

Thanks to @arkark (Takeshi Kaneko) of GMO Cybersecurity by Ierae, Inc. for disclosing this vulnerability.

vm2: Inspect Manipulation vm2: Sandbox Escape

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in vm2 ausnutzen, um beliebigen Programmcode auszuführen und um Dateien zu manipulieren.