ChromeWeb browser · Google
CVE-2022-0309
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 Autofill in Google Chrome prior to 97.0.4692.99 allowed a remote attacker to bypass navigation restrictions 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 confidenceGoogle Chrome's Autofill feature had an implementation flaw that allowed a remote attacker to bypass navigation restrictions through a specially crafted HTML page. This could enable malicious pages to manipulate autofill behavior in ways that circumvent security boundaries.
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.
-
Check installed Chrome versionNavigate to chrome://settings/help or use 'Google Chrome > About Google Chrome' menu to view the installed version numberAffected if The displayed version is below 97.0.4692.99 (e.g., 97.0.4692.71, 96.x.x.x, etc.)
-
Verify Autofill feature is enabledGo to chrome://settings/autofill or Settings > Autofill and passwords > Autofill services to confirm at least one autofill option (addresses, payment methods, passwords) is turned onAffected if Any Autofill service is enabled - the vulnerability exploits the autofill behavior when enabled
-
Check for recent autofill data anomaliesReview autofill entries at chrome://settings/addresses and chrome://settings/paymentMethods for unknown or suspicious entries that were not manually addedAffected if Unknown autofill profiles or payment methods exist that users do not recognize
-
Review browser history for unusual navigation patternsCheck Chrome history (Ctrl+H) for frequent visits to unfamiliar sites immediately followed by autofill-triggered actions, or look for rapid sequential visits without user interactionAffected if History shows patterns of page visits and form submissions that did not involve typical user navigation
You are affected if your Chrome version is below 97.0.4692.99 and Autofill is enabled, as the vulnerability requires the Autofill feature to be present for exploitation.
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 to patch the vulnerability. Organizations should ensure endpoint management systems push the browser update to all affected clients.
Chrome 97.0.4692.99 or later
- Open Google Chrome on your computer
- Click the three-dot menu icon in the top-right corner
- Select 'Help' from the dropdown menu
- Click 'About Google Chrome'
- Chrome will automatically check for updates; if version shown is below 97.0.4692.99, click 'Update Google Chrome'
- Restart the browser to apply the update
- Verify the version now shows 97.0.4692.99 or later via the same About Google Chrome page
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0309 — 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-0309 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