How to fix: Permissions-Policy grants camera to every origin
The policy grants camera to every origin (camera=*), which includes any third party the page embeds in an iframe. Granting it to the page's own origin, restricting it to an allowlist, or blocking it outright is not reported.
Why it matters
Set Permissions-Policy: camera=() to block entirely
camera=* hands the camera permission prompt to any embedded third-party frame, not just to this site. camera=(self) or camera=() keeps it with the page itself. A legacy Feature-Policy header is read with its own syntax (camera 'self'), which is restrictive and is not reported.
How to fix it
- 1Set Permissions-Policy: camera=() to block entirely
Code examples
Restrict camera access in Permissions-Policy
// next.config.mjs
export default {
async headers() {
return [{ source: "/(.*)", headers: [{ key: "Permissions-Policy", value: "camera=('self')" }] }];
},
};
// Blocks camera access for all third-party iframes by default
// Only allow your own origin to request camera permissionReferences
Detected automatically by VulnRadar. The check id is permissions-policy-camera-blocked, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Permissions-Policy grants camera to every origin?
- 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-camera-blocked, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Permissions-Policy grants camera to every origin 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.