ChromeWeb browser · Google
CVE-2022-4135
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 GPU in Google Chrome prior to 107.0.5304.121 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape 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 confidenceA heap buffer overflow vulnerability exists in the GPU (graphics processing unit) component of Google Chrome versions prior to 107.0.5304.121. An attacker who has already compromised the renderer process can exploit this buffer overflow to potentially escape the browser's sandbox isolation via a specially crafted HTML page.
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
< 107.0.5304.121< 107.0.1418.62< 107.0.5304.150CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 Google Chrome versionNavigate to chrome://version or click Help > About Google Chrome to see the full version numberAffected if Version is lower than 107.0.5304.121
-
Check installed Microsoft Edge versionNavigate to edge://version or click Help > About Microsoft Edge to see the full version numberAffected if Version is lower than 107.0.1418.62 (Legacy Edge) or 107.0.5304.150 (Chromium Edge)
-
Verify GPU hardware acceleration is enabledNavigate to chrome://gpu or edge://gpu and check if GPU compositing and rasterization are listed as enabledAffected if GPU acceleration is enabled and browser version is vulnerable - the flaw exists in the GPU component and requires it to be active
You are affected if your installed Chrome/Edge version is below the fixed releases AND GPU hardware acceleration is enabled in your browser settings.
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 · scoped107.0.1418.62107.0.5304.121107.0.5304.150
Update Google Chrome to version 107.0.5304.121 or later. Since exploitation requires a compromised renderer process, ensure defense-in-depth controls including browser sandboxing and network segmentation are properly configured.
Chrome 107.0.5304.121 or later; Edge 107.0.1418.62 or later; Edge Chromium 107.0.5304.150 or later
- Open Chrome, go to Menu > Help > About Google Chrome to check current version
- If version is below 107.0.5304.121, click 'Update Google Chrome' and restart
- For Microsoft Edge: Open Edge, go to Menu > Help and Feedback > About Microsoft Edge
- If Edge version is below 107.0.1418.62, the browser will automatically update; restart if needed
- Verify the update was successful by checking the version number again after restart
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Exploited in the wild — priority engagement
- 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-4135 — 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-4135 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