How to fix: setInterval with string arg
setInterval('code', 1000) is implicitly eval(). Pass a function reference instead.
Why it matters
Use setInterval(function() {}, 1000) instead of setInterval('...', 1000)
setInterval('code', 1000) is implicitly eval(). Pass a function reference instead.
How to fix it
- 1Use setInterval(function() {}, 1000) instead of setInterval('...', 1000)
Code examples
Pass function reference to setInterval
// BAD: string form is eval()
setInterval("updateClock()", 1000);
// GOOD: function reference
setInterval(updateClock, 1000);
setInterval(() => fetchData(endpoint), 5000);References
Detected automatically by VulnRadar. The check id is code-eval-setinterval-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 setInterval with string arg?
- VulnRadar rates this high 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-eval-setinterval-string, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does setInterval with string arg 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.