WebAuthn Level 3 Conditional Mediation Cross-Origin Boundary Standard

--- description: WebAuthn Level 3 Conditional Mediation Cross-Origin Boundary Standard - Enforces strict cryptographic origin binding and Permission-Policy verification for WebAuthn Level 3 conditional UI mediation embedded in cross-origin frames. Mandates server-side validation of clientDataJSON crossOrigin and topOrigin attributes alongside deterministic AbortController lifecycle management to eliminate credential harvesting and autofill mediation races. globs: src/**/*.{ts,tsx}, server/**/*.{ts,js} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/webauthn-l3-conditional-mediation-cross-origin-boundary-standard" --- # WebAuthn Level 3 Conditional Mediation Cross-Origin Boundary Standard > **Severity**: CRITICAL | **Category**: security > **Anti-Pattern Warning**: Unvalidated Cross-Origin Conditional Mediation and Unbounded Autofill Race Conditions ## System Constraints You are a Principal Engineer enforcing WebAuthn Level 3 Conditional Mediation Cross-Origin Boundary Standards. You must mandate strict adherence to WebAuthn L3 specifications for embedded conditional mediation (Passkey autofill). Ensure all cross-origin credential verification validates clientDataJSON flags ('crossOrigin', 'topOrigin') against authorized Related Origin manifests. Enforce explicit AbortController lifecycle management on all conditional mediation calls to prevent race conditions with modal authentication ceremonies. ## Strict Guidelines - Engineers MUST ALWAYS validate `crossOrigin` and `topOrigin` in `clientDataJSON` during server-side authentication response verification whenever requests originate from nested or federated contexts. - Engineers MUST verify that any cross-origin frame requesting passkey operations is explicitly permitted via HTTP header `Permissions-Policy: publickey-credentials-get=(self "https://trusted-origin.com")`. - Services MUST validate that top-level origins claiming credentials across boundaries are authorized via the target RP's `/.well-known/webauthn` Related Origin Requests (ROR) manifest. - Engineers MUST NOT invoke `navigator.credentials.get({ mediation: 'conditional', ... })` without an active `AbortSignal` tied to the lifecycle of the host input element. - Components NEVER allow concurrent conditional mediation and modal (`mediation: 'required'`) requests; pending conditional ceremonies MUST be explicitly aborted prior to dispatching modal ceremonies. ## Bad vs Good Implementations ### WebAuthn L3 Server-Side clientDataJSON Boundary Verification & Client Mediation Lifecycle #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: The verification function ignores WebAuthn Level 3 `crossOrigin` and `topOrigin` properties. If conditional mediation is requested within a nested browsing context or cross-origin iframe, an attacker can exploit federated contexts or cross-site embeddings without proving parent frame authorization. ```typescript import { Request, Response } from 'express'; interface ClientDataJSON { type: string; challenge: string; origin: string; } export async function verifyPasskeyAuthentication(req: Request, res: Response) { const { clientDataJSONBase64, expectedChallenge, expectedRpId } = req.body; const rawJson = Buffer.from(clientDataJSONBase64, 'base64').toString('utf8'); const clientData: ClientDataJSON = JSON.parse(rawJson); // VULNERABILITY: Blindly checks only origin, ignoring crossOrigin and topOrigin flags. // Malicious embedded iframes can harvest credentials or trigger autofill races. if (clientData.type !== 'webauthn.get') { return res.status(400).json({ error: 'Invalid operation type' }); } if (clientData.challenge !== expectedChallenge) { return res.status(400).json({ error: 'Challenge mismatch' }); } if (clientData.origin !== `https://${expectedRpId}`) { return res.status(400).json({ error: 'Origin mismatch' }); } return res.status(200).json({ verified: true }); } ``` #### Production Standard (Correct) > **Standard**: Production invariant compliant implementation ensuring memory safety, deterministic execution, and zero runtime hallucination. ```typescript import { Request, Response } from 'express'; interface WebAuthnLevel3ClientDataJSON { type: string; challenge: string; origin: string; crossOrigin?: boolean; topOrigin?: string; } // Pre-approved related top origins based on RFC / W3C Related Origin Requests const AUTHORIZED_TOP_ORIGINS = new Set<string>([ 'https://auth.example.com', 'https://checkout.example.com', ]); export async function verifyPasskeyAuthentication(req: Request, res: Response) { const { clientDataJSONBase64, expectedChallenge, expectedRpOrigin } = req.body; const rawJson = Buffer.from(clientDataJSONBase64, 'base64').toString('utf8'); const clientData: WebAuthnLevel3ClientDataJSON = JSON.parse(rawJson); if (clientData.type !== 'webauthn.get') { return res.status(400).json({ error: 'Invalid token ceremony type' }); } if (clientData.challenge !== expectedChallenge) { return res.status(400).json({ error: 'Cryptographic challenge mismatch' }); } // Strict WebAuthn L3 Origin & Cross-Origin Boundary Assertion if (clientData.origin !== expectedRpOrigin) { return res.status(403).json({ error: 'Credential origin mismatch' }); } if (clientData.crossOrigin === true) { if (!clientData.topOrigin || !AUTHORIZED_TOP_ORIGINS.has(clientData.topOrigin)) { return res.status(403).json({ error: 'Untrusted cross-origin topOrigin boundary detected', }); } } else if (clientData.crossOrigin === false && clientData.topOrigin !== undefined) { return res.status(400).json({ error: 'Malformed clientDataJSON boundary state' }); } return res.status(200).json({ verified: true }); } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: WebAuthn Level 3 Conditional Mediation Cross-Origin Boundary Standard

WebAuthn Level 3 Conditional Mediation Cross-Origin Boundary Standard defines an industrial-grade behavioral standard for security engineering. Enforces strict cryptographic origin binding and Permission-Policy verification for WebAuthn Level 3 conditional UI mediation embedded in cross-origin frames. Mandates server-side validation of clientDataJSON crossOrigin and topOrigin attributes alongside deterministic AbortController lifecycle management to eliminate credential harvesting and autofill mediation races. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Unvalidated Cross-Origin Conditional Mediation and Unbounded Autofill Race Conditions Without an explicit system instruction file, developers spend hours debugging silent failures.

Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Unvalidated Cross-Origin Conditional Mediation and Unbounded Autofill Race Conditions	Critical	Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production. Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture Inconsistency	AI assistants produce mixed paradigms across files, creating fragmented codebase conventions.	Medium	Increases cognitive load during code reviews and leads to maintenance debt across engineering teams. Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.

Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

Engineers MUST ALWAYS validate `crossOrigin` and `topOrigin` in `clientDataJSON` during server-side authentication response verification whenever requests originate from nested or federated contexts.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.