How to fix: JSON.parse piped into new Function
new Function('return ' + JSON.parse(input)) or new Function(JSON.parse(input).body) constructs a function body from parsed JSON. The parsed JSON still ships attacker-controlled source code.
Why it matters
Function constructor evaluates attacker-controlled source, enabling arbitrary code execution.
The `code-deser-jsonparse-newfunction` check verifies that the server does not expose the `deser-jsonparse-newfunction` 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
- 1Avoid new Function for untrusted input; use real functions or modules.
- 2If dynamic logic is required, evaluate it through a safe DSL like JSONLogic.
- 3Add CSP to block inline scripts even if injection succeeds.
Code examples
Use JSON.parse, not new Function for JSON
// BAD: new Function is eval in disguise
const data = (new Function("return " + jsonString))();
// GOOD: use the built-in JSON parser
const data = JSON.parse(jsonString);
// Validate with a schema library for extra safetyReferences
Detected automatically by VulnRadar. The check id is code-deser-jsonparse-newfunction, 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 JSON.parse piped into new Function?
- 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-jsonparse-newfunction, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does JSON.parse piped into new Function map to?
- It maps to CWE-94. In the OWASP Top 10 it falls under A03: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.