ChromeWeb browser · Google
CVE-2022-3370
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 · uneditedUse after free in Custom Elements in Google Chrome prior to 106.0.5249.91 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
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 confidenceUse-after-free vulnerability in Google Chrome's Custom Elements implementation prior to version 106.0.5249.91 allows a remote attacker to corrupt heap memory via a maliciously crafted HTML page, potentially leading to arbitrary code execution.
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
< 106.0.5249.91CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 version via chrome://versionType chrome://version in the Chrome address bar and press Enter. Note the version number displayed in the 'Google Chrome' fieldAffected if The version number shown is less than 106.0.5249.91 (for example, 106.0.5249.62 or earlier)
-
Check Chrome version via command lineOpen a command prompt or terminal and run 'chrome --version' or on Windows '"C:\Program Files\Google\Chrome\Application\chrome.exe" --version'Affected if The reported version is earlier than 106.0.5249.91
-
Check Chrome version via Help menuClick the three-dot menu in Chrome, select Help, then select About Google ChromeAffected if The About Chrome page shows a version number below 106.0.5249.91 or indicates an update is available
-
Check for pending Chrome updatesNavigate to chrome://settings/help to view current version and update availability statusAffected if Chrome indicates an update is available or the version listed is below 106.0.5249.91
User is affected if the installed Google Chrome version is less than 106.0.5249.91 and the browser is used to render web content containing Custom Elements
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 · scoped106.0.5249.91
Update Google Chrome to version 106.0.5249.91 or later; deploy browser update policies across the organization to ensure all endpoints are patched.
Chrome 106.0.5249.91 or later
- Open Google Chrome browser
- Click the three-dot menu icon in the upper-right corner
- Select 'Help' from the dropdown menu
- Select 'About Google Chrome'
- Chrome will automatically check for and install updates
- If version is below 106.0.5249.91, wait for update to download and install
- Restart the browser to complete the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3370 — 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-3370 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