CyberRota Analysis
AI-GeneratedThe vulnerability allows untrusted guest code in vm2 versions up to 3.12.0 to invoke Node.js's crypto.setFips() function, potentially altering the FIPS mode of the entire host process. This breach of isolation can lead to unauthorized changes in cryptographic settings, impacting the security posture of applications relying on FIPS compliance. Organizations utilizing vm2 for sandboxing Node.js applications should prioritize upgrading to version 3.12.1 to mitigate this risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
vm2 through 3.12.0 exposes Node.js's crypto.setFips() function to untrusted guest code when an embedder explicitly allowlists the crypto builtin for a NodeVM (require.builtin: ['crypto']). The builtin sanitizer (sanitizeCryptoModule in lib/builtin.js) replaces crypto.setEngine but leaves crypto.setFips callable, and the readonly wrapper used to expose the host module does not localize side effects of forwarded host functions. Guest code can therefore call crypto.setFips() to change the FIPS mode of the entire host process; the modified mode is subsequently observed by trusted host code (crypto.getFips() changed from 0 to 1 in the reported test), crossing the NodeVM isolation boundary. Fixed in vm2 3.12.1.