ChromeWeb browser · Google
CVE-2022-4437
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 Mojo IPC in Google Chrome prior to 108.0.5359.124 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 Mojo IPC (Inter-Process Communication) component of Google Chrome prior to version 108.0.5359.124. A remote attacker can exploit this by tricking users into visiting a crafted HTML page, leading to heap corruption and potentially remote 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
< 108.0.5359.124CVSS 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.
-
Confirm Google Chrome is installedCheck for Chrome executable or browser presence. On Windows: look in Program Files\Google\Chrome\Application\chrome.exe. On macOS: look in /Applications/Google Chrome.app. On Linux: run which google-chrome or which chromium-browserAffected if Google Chrome browser is present on the system
-
Retrieve installed Chrome versionOpen chrome://version in the Chrome address bar, or run 'google-chrome --version' (Linux) or 'chrome --version' from command line. On Windows, right-click chrome.exe > Properties > Details > File VersionAffected if Unable to determine version indicates manual investigation needed
-
Compare version against vulnerable rangeTake the installed version number and compare it numerically to 108.0.5359.124Affected if Installed version is less than 108.0.5359.124 (for example 107.x.x.x, 106.x.x.x, etc.)
-
Assess web browsing exposureDetermine if the Chrome installation is used for web browsing. This vulnerability is triggered by visiting a crafted malicious HTML pageAffected if Chrome is used for web browsing and version is below 108.0.5359.124
The environment is affected if Google Chrome is installed with a version lower than 108.0.5359.124 and the browser is used for web browsing, allowing potential exposure to malicious HTML pages.
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 · scoped108.0.5359.124
Update Google Chrome to version 108.0.5359.124 or later to patch the vulnerability.
Chrome 108.0.5359.124 or later
- Open Google Chrome
- Navigate to Settings > Help > About Google Chrome
- Chrome will automatically check for updates
- If an update is available, download and install version 108.0.5359.124 or later
- Restart the browser to apply the 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
- 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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-4437 — 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-4437 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