ChromeWeb browser · Google
CVE-2022-0305
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInappropriate implementation in Service Worker API in Google Chrome prior to 97.0.4692.99 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn inappropriate implementation in Chrome's Service Worker API prior to version 97.0.4692.99 allowed a renderer process that was already compromised to bypass site isolation protections, potentially allowing access to cross-origin resources that should be protected.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
< 97.0.4692.99CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Google Chrome is installedCheck for Chrome installation - on Windows look in Program Files/Google/Chrome/Application/chrome.exe, on macOS in /Applications/Google Chrome.app, or run 'google-chrome --version' or 'chrome --version' in terminalAffected if Google Chrome is not installed on the system
-
Determine installed Chrome versionOpen Chrome, click the three-dot menu > Help > About Google Chrome, or enter chrome://settings/help in the address bar, or run 'google-chrome --version' in command lineAffected if Version shown is below 97.0.4692.99 (e.g., 96.x.x.x or earlier)
-
Confirm Service Worker API usage contextThis vulnerability requires a compromised renderer process - check if the browser has been used to visit untrusted or compromised websites. Review browser history for suspicious sites.Affected if Untrusted websites were visited while using an affected Chrome version, and the renderer process may have been compromised
User is affected if Google Chrome version is below 97.0.4692.99 and the browser was used to visit potentially compromised websites that could have exploited the Service Worker API flaw to bypass site isolation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped97.0.4692.99
Update Google Chrome to version 97.0.4692.99 or later. Organizations should ensure automated browser update policies are enforced across endpoints.
Chrome 97.0.4692.99 or later (stable channel)
- Open Google Chrome and navigate to chrome://settings/help
- Click 'Check for updates' or wait for Chrome to automatically check
- Allow Chrome to download and install the update (version 97.0.4692.99 or later)
- Restart Google Chrome to apply the security update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0305 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-0305 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data