Remote code execution via hard-coded vulnerable vm2
Published May 8, 2023 · Updated Jan 28, 2025
Code injection in jsreport before 3.11.3 allows remote attackers to execute code with the playground server's authority. The jsreport-core package hard-codes a vm2 release whose sandbox fails to isolate untrusted JavaScript from its host process. No authentication or user interaction is required; successful exploitation grants the server process's privileges on the host.
Summary
What happened
Code injection in jsreport before 3.11.3 allows remote attackers to execute code with the playground server's authority. The jsreport-core package hard-codes a vm2 release whose sandbox fails to isolate untrusted JavaScript from its host process. No authentication or user interaction is required; successful exploitation grants the server process's privileges on the host.
The record
- CVE
- CVE-2023-2583
- Published
- May 8, 2023
- Updated
- Jan 28, 2025
- Vendor
- jsreport
- Product
- jsreport
- Classifications
- CWE-94, T1059.007, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 8, 2023CVE publishedPublication date reported by the CVE source.
- Jan 28, 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=unspecified <3.11.3
What conditions does exploitation require?
What is affected?
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
- huntr jsreport vm2 sandbox-escape proof of conceptproof of concept · unverified
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