CVE-2022-1309

This is a Chrome sandbox escape: insufficient policy enforcement in the browser's developer tools lets a crafted HTML page break out of the renderer sandbox. The sandbox is the wall that contains malicious web content, so an escape means a page a victim merely visits can reach beyond the tab into the broader system. It needs the victim to interact — visiting the page — but requires no privileges and works remotely against any user running a pre-100.0.4896.88 Chrome.

Browser bugs like this are the drive-by attacker's staple: the delivery is just getting someone to load a URL, achievable through phishing, malvertising, or a compromised site. Sandbox escapes are high-value because they're the piece that turns contained web content into real footholds, and they're frequently chained with a renderer bug into a full one-click compromise. Chrome's install base is enormous and mostly on auto-update, which is the saving grace — the patched build rolls out widely and fast — but any user or fleet that lags on updates is exposed to a well-understood, actively-hunted class of flaw.

Browsers are the one place where auto-update usually does our job for us, so our angle is update-coverage assurance rather than heroics. The task is confirming the fleet's Chrome is actually at or past 100.0.4896.88 — auto-update stragglers, managed installs with pinned versions, and machines that rarely restart are where the risk concentrates. We'd rank it by that update-lag population and lean on our endpoint management to force the browser version, since the vendor fix is the fix and reachability is universal.