ChromeWeb browser · Google
CVE-2022-3200
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 · uneditedHeap buffer overflow in Internals in Google Chrome prior to 105.0.5195.125 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 confidenceHeap buffer overflow vulnerability in Google Chrome's Internals component allows remote attackers to exploit heap corruption via malicious HTML pages. The vulnerability exists in versions prior to 105.0.5195.125 and could allow arbitrary code execution or complete system compromise.
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
< 105.0.5195.125
FedoraOperating system
= 37CVSS 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 versionOpen chrome://version in the browser address bar, or run 'google-chrome --version' or 'chrome --version' from command line. On Linux, also try 'rpm -q google-chrome-stable' or 'dpkg -l | grep chrome'Affected if The displayed version number is less than 105.0.5195.125 (for example, 105.0.5195.102, 104.x.x.x, etc.)
-
Verify Chrome is not ChromiumConfirm the browser is Google Chrome specifically, not Chromium or other Chromium-based browsers. Check the browser name in chrome://version or the application name in the task managerAffected if The browser is Google Chrome but the version falls below 105.0.5195.125. Chromium-based browsers may have different version numbers and patching timelines
-
Check if Internals component is accessibleNavigate to chrome://internals in the browser address bar. This component handles internal browser utilities and debugging featuresAffected if The page loads successfully, indicating the Internals component is enabled and accessible in the browser
You are affected if your Google Chrome version is below 105.0.5195.125 and the Internals component is accessible in the browser.
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 · scoped105.0.5195.125
Update Google Chrome to version 105.0.5195.125 or later to patch the heap buffer overflow vulnerability.
Chrome 105.0.5195.125 (or any subsequent stable release)
- For Chrome/Chromium browser users: Open Chrome, go to Settings > Help > About Google Chrome, and verify the version is 105.0.5195.125 or later. If not, click 'Update Google Chrome' and restart the browser.
- For Fedora 37 systems: Run 'sudo dnf update google-chrome-stable' or 'sudo dnf update chromium' to apply security patches.
- Verify the update was successful by checking the version again in Chrome > Settings > Help > About Google Chrome.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3200 — 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-3200 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