How to fix: node-serialize deserialize()
node-serializes serialize/deserialize supports an IIFE payload (rce: _$ND_FUNC$$ = function(){...}()). The deserialize() call evaluates that payload and executes attacker JavaScript on the server.
Why it matters
Untrusted serialized input is evaluated, leading directly to remote code execution.
The `code-deser-node-serialize` check verifies that the server does not expose the `deser-node-serialize` weakness in the code category. The detection runs against the response headers, body, or auxiliary probes (DNS, TLS, async fetch) as appropriate.
How to fix it
- 1Replace node-serialize with JSON.parse; node-serialize is unmaintained and unsafe.
- 2Validate any unserialized data with a strict schema (Zod, Joi).
- 3Block the package via package.json overrides or denoising rules.
Code examples
Avoid node-serialize: use JSON.parse instead
// BAD: node-serialize.unserialize() is vulnerable to RCE
import serialize from "node-serialize";
const data = serialize.unserialize(userInput); // RCE if input contains IIFE
// GOOD: use JSON.parse or a safe serialization library
const data = JSON.parse(userInput);
// Validate the parsed object against a schemaReferences
Detected automatically by VulnRadar. The check id is code-deser-node-serialize, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is node-serialize deserialize()?
- VulnRadar rates this critical severity in the code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id code-deser-node-serialize, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does node-serialize deserialize() map to?
- It maps to CWE-502. In the OWASP Top 10 it falls under A08:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.