Evaluating Mitigations & Vulnerabilities in Chrome

The Chrome Security Team outlines a threat model for browser code execution and a framework to evaluate attacker utility—emphasizing factors like reliability, low interaction, ubiquity, scriptability, stealth, and longevity—to guide mitigation priorities. It advocates incremental hardening (e.g., memory safety via Rust, sandboxing, detection like GWP-ASan) and the removal of escalation paths to raise attacker costs across diverse adversaries, arguing that even partial reductions in exploit utility meaningfully reduce overall user risk.