How to fix: setTimeout/setInterval with String
Timer functions with string argument.
Why it matters
String arguments are eval'd, enabling code injection.
setTimeout('code', 0) is equivalent to eval('code').
How to fix it
- 1Pass functions, not strings, to setTimeout/setInterval.
Code examples
Pass a function reference, not a string
// BAD: string form evaluates code like eval()
setTimeout("doSomething()", 1000);
// GOOD: pass a function reference
setTimeout(doSomething, 1000);
setTimeout(() => doSomethingWith(arg), 1000);References
Detected automatically by VulnRadar. The check id is settimeout-string, 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 setTimeout/setInterval with String?
- VulnRadar rates this medium 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 settimeout-string, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does setTimeout/setInterval with String 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.