CVE-2023-32313: Inspect method manipulation in vm2

Published May 15, 2023
·
Updated

A flaw was found in the vm2. After making a vm, the inspect method is read-write for console.log, which allows an attacker to edit options for console.log. This issue impacts the integrity by changing the log subsystem.

Other sources

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

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

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 Software

3 affected componentsFixes available
npm/vm2<3.9.18
3.9.18
redhat/vm2<3.9.18
3.9.18
Vm2 Project Vm2 Node.js<3.9.18

Remediation

Information

After creating a vm, make the inspect method readonly with vm.readonly(inspect).

Event History

May 15, 2023
CVE Published
12:00 AM
Data Sourced
12:00 AM
RemedyDescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·07:45 PM
Data Sourced
via MITRE·07:45 PM
DescriptionSeverityWeakness
May 17, 2023
Advisory Published
03:49 AM

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2023-32313?

CVE-2023-32313 is classified as a medium severity vulnerability.

2

How do I fix CVE-2023-32313?

To fix CVE-2023-32313, upgrade vm2 to version 3.9.18 or later.

3

What impact does CVE-2023-32313 have on my system?

CVE-2023-32313 can compromise the integrity of your logging subsystem by allowing modification of console.log options.

4

Which versions of vm2 are affected by CVE-2023-32313?

CVE-2023-32313 affects vm2 versions 3.9.17 and lower.

5

Who is responsible for the vm2 project related to CVE-2023-32313?

The vm2 project related to CVE-2023-32313 is maintained by the vm2 Project.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203