How to fix: CSP Missing default-src Fallback
CSP has no default-src directive.
Why it matters
Undeclared resource types are completely unrestricted.
default-src acts as a fallback for all unspecified directives.
How to fix it
- 1Add default-src 'self' as a baseline to your CSP.
Code examples
Add default-src to CSP
// default-src is the fallback for all resource types not otherwise specified
export default {
async headers() {
return [{ source: "/(.*)", headers: [{
key: "Content-Security-Policy",
value: "default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; object-src 'none'; frame-ancestors 'none';"
}]}];
},
};References
Detected automatically by VulnRadar. The check id is csp-no-default-src, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is CSP Missing default-src Fallback?
- VulnRadar rates this low 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-no-default-src, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does CSP Missing default-src Fallback map to?
- It maps to CWE-693. In the OWASP Top 10 it falls under A05: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.