How to fix: CSP allows data: URIs in script or object sources
The Content-Security-Policy permits data: URIs as a script or object source, enabling data-URI-based script execution.
Why it matters
Allowing data: in script-src allows attackers to execute base64-encoded scripts via XSS; this is functionally similar to allowing unsafe-inline and bypasses many CSP protections.
data: URIs in script-src are treated as unsafe by CSP Level 3. Remove data: from any security-critical directive.
How to fix it
- 1Remove data: from script-src and object-src
- 2Limit data: to img-src or font-src where needed for inline images or fonts
- 3Use nonces for any inline scripts that were previously base64-encoded data URIs
Code examples
Safe data: usage
// next.config.mjs
export default {
async headers() {
return [{ source: "/(.*)", headers: [{ key: "Content-Security-Policy", value: "default-src 'self'; script-src 'self'; img-src 'self' data:; font-src 'self' data:; object-src 'none';" }] }];
},
};References
Detected automatically by VulnRadar. The check id is csp-data-uri-allowed, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is CSP allows data: URIs in script or object sources?
- VulnRadar rates this medium 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-data-uri-allowed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does CSP allows data: URIs in script or object sources 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.