How to fix: Permissions-Policy otp-credentials allowed
Permissions-Policy does not restrict the otp-credentials directive (WebOTP API), leaving SMS OTP auto-fill available to any embedded frame by default.
Why it matters
A third-party iframe embedded on the page could request access to the WebOTP API and intercept one-time-passcode SMS messages intended for the top-level site.
The WebOTP API lets a page read verification codes from incoming SMS. Restricting it to 'self' (or blocking it entirely on pages that don't use it) prevents embedded third parties from requesting the same access.
How to fix it
- 1Set Permissions-Policy: otp-credentials=(self) or otp-credentials=() if unused.
Code examples
Restrict WebOTP access
// next.config.mjs
export default {
async headers() {
return [{ source: "/(.*)", headers: [{ key: "Permissions-Policy", value: "otp-credentials=(self)" }] }];
},
};References
Detected automatically by VulnRadar. The check id is permissions-policy-otp-credentials-blocked, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Permissions-Policy otp-credentials 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-otp-credentials-blocked, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Permissions-Policy otp-credentials 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.