ChromeWeb browser · Google
CVE-2022-3653
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 Vulkan in Google Chrome prior to 107.0.5304.62 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 · moderate confidenceHeap buffer overflow vulnerability in the Vulkan graphics API implementation in Google Chrome allows remote code execution through heap corruption. Attackers exploit this by tricking users into visiting specially crafted HTML pages that trigger the overflow in the Vulkan driver, potentially leading to arbitrary code execution in the browser process context.
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.62CVSS 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.
-
Determine installed Chrome versionOpen Chrome, click the three-dot menu > Help > About Google Chrome, or navigate to chrome://settings/helpAffected if The displayed version is less than 107.0.5304.62 (for example, 107.0.5304.0 or any earlier version)
-
Check if Vulkan API is enabledNavigate to chrome://gpu in the Chrome address bar and look for the 'Vulkan' section under Graphics Feature StatusAffected if Vulkan is listed as Enabled or hardware acceleration is enabled, indicating the vulnerable code path could be reached
-
Verify GPU rendering is activeNavigate to chrome://gpu and check if GPU-based compositing or hardware acceleration is enabledAffected if Hardware acceleration is turned on, meaning the Vulkan driver would be loaded and the overflow could occur
You are affected if your Chrome version is below 107.0.5304.62 AND Vulkan hardware acceleration is enabled in the 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.5304.62
Update Google Chrome to version 107.0.5304.62 or later. Organizations should deploy browser updates through their patch management infrastructure.
Chrome 107.0.5304.62 or later (stable channel)
- Open Google Chrome and navigate to Help > About Google Chrome to check the current version
- If the version is earlier than 107.0.5304.62, Chrome will automatically check for and prompt you to install the latest update
- Alternatively, download the latest stable version of Google Chrome from the official website (google.com/chrome)
- Restart Chrome after the update completes to apply the changes
- Verify the version now shows 107.0.5304.62 or later
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-3653 — 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-3653 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