Host console disruption via writable inspect reference
Published May 15, 2023 · Updated Jan 22, 2025
Improper isolation in Patrik Simek vm2 3.9.17 and earlier allows remote attackers to modify host console.log behavior via sandboxed code. A custom nodejs.util.inspect.custom hook receives the host util.inspect function during Buffer error formatting, and vm2 exposes that reference as writable. Execution of attacker-controlled JavaScript inside a VM instance is required; changing inspect.colors can make later host console.log calls throw a TypeError.
Summary
What happened
Improper isolation in Patrik Simek vm2 3.9.17 and earlier allows remote attackers to modify host console.log behavior via sandboxed code. A custom nodejs.util.inspect.custom hook receives the host util.inspect function during Buffer error formatting, and vm2 exposes that reference as writable. Execution of attacker-controlled JavaScript inside a VM instance is required; changing inspect.colors can make later host console.log calls throw a TypeError.
The record
- CVE
- CVE-2023-32313
- Published
- May 15, 2023
- Updated
- Jan 22, 2025
- Vendor
- Patrik Simek
- Product
- vm2
- Classifications
- CWE-74, T1565.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 15, 2023CVE publishedPublication date reported by the CVE source.
- Jan 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.9.18
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- PoC for breaking console.log in [email protected]proof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo