ChromeWeb browser · Google
CVE-2022-2007
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 WebGPU in Google Chrome prior to 102.0.5005.115 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
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 Chrome's WebGPU implementation prior to version 102.0.5005.115 allows remote attackers to corrupt heap memory via a malicious 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
< 102.0.5005.115
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 versionNavigate to chrome://settings/help in Chrome, or run 'google-chrome --version' or 'chrome --version' from command lineAffected if Version number is less than 102.0.5005.115 (for example, 102.0.5005.61 or earlier)
-
Confirm WebGPU is accessibleVisit chrome://gpu and look for 'WebGPU' in the 'Graphics Feature Status' section, or check if the WebGPU API is available in chrome://flagsAffected if WebGPU is listed as enabled or available in chrome://gpu output
-
Verify WebGPU is actually in useIf WebGPU is enabled, check whether any internal applications, extensions, or internal pages are actively using WebGPU by inspecting chrome://tracing with WebGPU category enabled, or check browser usage logs if availableAffected if WebGPU is actively being used by any page, extension, or internal component in the browser session
User is affected if Chrome version is below 102.0.5005.115 and WebGPU feature is enabled or actively used in the browser environment.
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 · scoped102.0.5005.115
Update Google Chrome to version 102.0.5005.115 or later; organizations may need to deploy browser updates through enterprise management tools.
Chrome 102.0.5005.115 or later (or latest stable release)
- Update Google Chrome to version 102.0.5005.115 or later by navigating to chrome://settings/help and clicking 'Update Google Chrome'
- Alternatively, download the latest Chrome version from the official Google Chrome website
- For Fedora 37 systems, run 'dnf update' or 'dnf upgrade' to apply available security patches for the chromium package
- Restart the browser after updating to ensure the fix is applied
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2007 — 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-2007 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