ChromeWeb browser · Google
CVE-2022-3041
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 WebSQL in Google Chrome prior to 105.0.5195.52 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 WebSQL component of Google Chrome versions prior to 105.0.5195.52 allows a remote attacker to exploit heap corruption via a malicious 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
< 105.0.5195.52
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, click the three-dot menu, select Help, then About Google Chrome. Alternatively, navigate to chrome://version/ in the address bar.Affected if The version shown is earlier than 105.0.5195.52 (e.g., 104.x.x.x or earlier)
-
Verify WebSQL component statusIn Chrome address bar, navigate to chrome://settings/content. Look for the WebSQL setting under the Databases section, or search for 'WebSQL' in Chrome settings.Affected if WebSQL is explicitly enabled or allowed in the browser settings (note: WebSQL was deprecated but could still be present in older versions)
-
Check if legacy WebSQL APIs are accessibleOpen Developer Tools (F12), go to the Console tab, and attempt to execute: if (window.openDatabase) { console.log('WebSQL available'); } else { console.log('WebSQL not available'); }Affected if The console returns 'WebSQL available', indicating the WebSQL component is present and potentially accessible
-
For Fedora systems, check installed package versionOpen a terminal and run: dnf list installed google-chrome-stable (or rpm -qa | grep chrome)Affected if The package version listed is earlier than the patched version available in Fedora 37 repositories
You are affected if Chrome version is below 105.0.5195.52 AND the WebSQL component is present/enabled in your 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.52
Update Google Chrome to version 105.0.5195.52 or later to patch the vulnerability; enterprise deployments may require testing for compatibility with internal applications.
Chrome 105.0.5195.52 or later
- 1. Open Google Chrome browser
- 2. Navigate to Chrome Settings > Help > About Google Chrome
- 3. Chrome will automatically check for and install the latest version
- 4. Wait for version 105.0.5195.52 or later to be installed
- 5. Restart the browser to complete the update
- 6. Verify the version by returning to About Google Chrome and confirming the version number
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3041 — 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-3041 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