InfoCode
How to fix: WebAuthn/Passkey Implementation
WebAuthn API usage detected.
Why it matters
Strong authentication method.
WebAuthn enables passwordless authentication.
How to fix it
- 1Ensure proper implementation.
Code examples
WebAuthn: verify attestation server-side
// Client: create credential
const credential = await navigator.credentials.create({ publicKey: options });
// Send to server for attestation verification
const res = await fetch("/api/auth/register", {
method: "POST",
body: JSON.stringify(credential),
});
// Server MUST verify the attestation using a library like SimpleWebAuthn
// Never skip server-side verificationReferences
Detected automatically by VulnRadar. The check id is webauthn-usage, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is WebAuthn/Passkey Implementation?
- VulnRadar rates this info severity in the code 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 webauthn-usage, which stays the same between runs so you can filter, diff, or gate CI on it.
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.