How to fix: Permissions-Policy attribution-reporting allowed
Permissions-Policy does not block the attribution-reporting directive, leaving the Privacy Sandbox Attribution Reporting API available to any script on the page.
Why it matters
Third-party scripts embedded on the page can register attribution sources/triggers on the visitor's behalf without an explicit site opt-in.
Attribution Reporting is part of Chrome's Privacy Sandbox. Sites that don't intend to participate in ad-attribution measurement should explicitly disable it via Permissions-Policy.
How to fix it
- 1Set Permissions-Policy: attribution-reporting=()
Code examples
Block Attribution Reporting API
// next.config.mjs
export default {
async headers() {
return [{ source: "/(.*)", headers: [{ key: "Permissions-Policy", value: "attribution-reporting=()" }] }];
},
};References
Detected automatically by VulnRadar. The check id is permissions-policy-attribution-reporting-blocked, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Permissions-Policy attribution-reporting allowed?
- 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 permissions-policy-attribution-reporting-blocked, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Permissions-Policy attribution-reporting allowed 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.