← All reports

Recognize credentialless COEP and DIP values behind a preference

Component: WebCore loader | 5752914

Cross-Origin-Embedder-Policy (COEP) and Document-Isolation-Policy (DIP) gate cross-origin isolation: a document that opts in must ensure every cross-origin subresource allows embedding, enforced per load by a CORP check, including in the network process. In the spec, credentialless is the relaxed variant that sends no-cors requests without credentials. Behind the new unstable CrossOriginEmbedderPolicyCredentiallessEnabled preference (off by default), WebKit now parses COEP: credentialless and DIP: isolate-and-credentialless and treats both as isolation-compatible. Checks that tested == RequireCORP now test != UnsafeNone/!= None, the new values cross NetworkProcess/WebProcess IPC, and service and shared workers with isolation-compatible policies share a context connection. Credential omission is not implemented yet, so CORP is still required for every cross-origin no-cors response.

This opens a second route to crossOriginIsolated (SharedArrayBuffer, high-resolution timers), and its own FIXME says it cannot ship until Local Network Access or ORB lands.

When a security enum gains a value and == checks flip to negated != checks, any missed site silently treats the new value as unisolated, or as isolated without enforcement. Grep for remaining RequireCORP/IsolateAndRequireCORP comparisons outside the converted sites, and for code assuming the enums are two-valued (they moved from : bool to : uint8_t). Confirm deserialization rejects out-of-range values so a compromised WebProcess cannot send a policy that inflates isolation. contextConnectionCrossOriginEmbedderPolicyValue normalizes Credentialless to RequireCORP for workers; check that the normalization is applied everywhere a context connection is selected or compared. Look for paths (redirects, worker script loads, blob/about:blank inheritance, the CredentiallessSupport::No reset) where a policy is downgraded or inherited incorrectly.