InfoHeaders
How to fix: CSP script-src Too Restrictive
CSP script-src only allows 'self'.
Why it matters
May break functionality if external scripts needed.
Very restrictive CSP may require code changes.
How to fix it
- 1Verify site functions correctly with this CSP.
Code examples
Add strict-dynamic with nonce to script-src 'self'
// 'self' alone allows any same-origin script, too broad
// Use nonce + strict-dynamic for better control:
import { randomBytes } from "crypto";
const nonce = randomBytes(16).toString("base64");
res.setHeader("Content-Security-Policy",
`script-src 'nonce-${nonce}' 'strict-dynamic'; object-src 'none'; base-uri 'none';`
);References
Detected automatically by VulnRadar. The check id is csp-script-src-self-only, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is CSP script-src Too Restrictive?
- VulnRadar rates this info severity in the headers 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 csp-script-src-self-only, which stays the same between runs so you can filter, diff, or gate CI on it.
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.