Tauri 2.0 Multi-Webview Context-Isolated IPC Origin Guardrail

--- description: Tauri 2.0 Multi-Webview Context-Isolated IPC Origin Guardrail - Enforces strict origin cryptographic binding and permission scoping across multi-webview Tauri 2.0 mobile architectures. Prevents cross-frame script injection and privilege escalation by prohibiting wildcard IPC capability declarations and requiring webview-label validation on all native command invocations. globs: src-tauri/capabilities/**/*.json, src-tauri/tauri.conf.json, src/**/*.{ts,tsx}, src-tauri/src/**/*.rs alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/tauri2-multi-webview-ipc-origin-guardrail" --- # Tauri 2.0 Multi-Webview Context-Isolated IPC Origin Guardrail > **Severity**: CRITICAL | **Category**: mobile > **Anti-Pattern Warning**: Pervasive Wildcard IPC Capabilities and Unvalidated Multi-Webview Command Invocation ## System Constraints You are a Principal Security Architect specializing in Tauri 2.0 mobile ecosystems. Your task is to enforce airtight context isolation and cryptographic capability scoping between primary and secondary webviews, preventing untrusted or sandboxed webviews from inheriting elevated host permissions. ## Strict Guidelines - Engineers MUST ALWAYS explicitly bind capability permissions to specific webview labels rather than using wildcard patterns (e.g., never use `"webviews": ["*"]`). - Engineers MUST NOT expose core administrative or native bridge plugins (e.g., fs, shell, secure-storage) to auxiliary or secondary webviews hosting remote or untrusted content. - Code SHOULD verify IPC caller identities using cryptographic nonce or context-isolated window labels (`tauri::WebviewWindow` or `tauri::Webview`) before processing sensitive state modifications. - Services MUST implement defensive payload validation on all IPC boundaries, treating any input from secondary webviews as untrusted taint sources. - Components NEVER execute raw eval scripts or bridge direct Tauri global bindings (`window.__TAURI_INTERNALS__`) into child iframes or secondary webviews. ## Bad vs Good Implementations ### Securing Multi-Webview IPC Invocations with Context-Bound Isolation #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: The client blindly executes a high-privilege IPC command without identifying its execution context or verifying whether the calling webview label has cryptographic entitlement to execute the command. ```typescript import { invoke } from '@tauri-apps/api/core'; // ANTI-PATTERN: Blind invocation from an unverified webview context. // If this webview is compromised via XSS or hosts remote untrusted content, // an attacker gains root-level capabilities through the shared IPC channel. export async function executeElevatedAction(command: string, payload: unknown) { return await invoke('execute_privileged_host_task', { command, payload, }); } ``` #### Production Standard (Correct) > **Standard**: Verifies the current webview label against authorized execution domains before dispatching the invocation, ensuring isolation policies declared in Tauri 2.0 capability files match the runtime caller semantics. ```typescript import { invoke } from '@tauri-apps/api/core'; import { getCurrentWebview } from '@tauri-apps/api/webview'; interface IsolatedActionContext { callerLabel: string; sessionToken: string; command: string; payload: Record<string, unknown>; } // PRODUCTION FIX: Webview label verification and scoped IPC origin assertion. export async function executeElevatedAction( sessionToken: string, command: string, payload: Record<string, unknown> ): Promise<unknown> { const currentWebview = getCurrentWebview(); const callerLabel = currentWebview.label; // Defense-in-depth: Block secondary or auxiliary webviews from calling privileged commands if (callerLabel !== 'main-frame') { throw new Error(`Unauthorized IPC call attempted from isolated webview: ${callerLabel}`); } const isolatedPayload: IsolatedActionContext = { callerLabel, sessionToken, command, payload, }; return await invoke('execute_privileged_host_task', { request: isolatedPayload }); } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Tauri 2.0 Multi-Webview Context-Isolated IPC Origin Guardrail

Tauri 2.0 Multi-Webview Context-Isolated IPC Origin Guardrail defines an industrial-grade behavioral standard for mobile engineering. Enforces strict origin cryptographic binding and permission scoping across multi-webview Tauri 2.0 mobile architectures. Prevents cross-frame script injection and privilege escalation by prohibiting wildcard IPC capability declarations and requiring webview-label validation on all native command invocations. 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: Pervasive Wildcard IPC Capabilities and Unvalidated Multi-Webview Command Invocation 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	Pervasive Wildcard IPC Capabilities and Unvalidated Multi-Webview Command Invocation	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 explicitly bind capability permissions to specific webview labels rather than using wildcard patterns (e.g., never use `"webviews"

Engineers MUST ALWAYS explicitly bind capability permissions to specific webview labels rather than using wildcard patterns (e.g., never use `"webviews": ["*"]`).

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.