ChromeWeb browser · Google
CVE-2022-1853
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 Indexed DB in Google Chrome prior to 102.0.5005.61 allowed a remote attacker to potentially perform a sandbox escape 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 Indexed DB component of Google Chrome (versions prior to 102.0.5005.61) allows a remote attacker to execute arbitrary code via a crafted HTML page, potentially escaping the browser's sandbox isolation.
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.61CVSS 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.
-
Determine installed Chrome versionOpen chrome://version in the Chrome address bar and note the version number under 'Google Chrome'Affected if Version is less than 102.0.5005.61
-
Confirm Chrome is up to date via UIClick the three-dot menu > Help > About Google Chrome to view the current version and check if updates are availableAffected if The displayed version shows a number lower than 102.0.5005.61 or indicates an update is available
-
Verify Indexed DB feature is enabledIndexed DB is enabled by default; to confirm, go to chrome://settings/privacy, scroll to 'Site Settings', click 'Additional content settings', and ensure Indexed DB is not blocked or set to 'Blocked'Affected if Indexed DB is explicitly blocked (vulnerability requires it to be enabled for exploitation)
-
Check for recent browser process crashesReview Chrome's crash reports in chrome://crashes if available, or check system event logs for recent chrome.exe crash eventsAffected if Recent crashes occurred after visiting untrusted websites, as this may indicate exploitation attempts
You are affected if your Chrome version is below 102.0.5005.61 and Indexed DB is not explicitly blocked in 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 · scoped102.0.5005.61
Update Google Chrome to version 102.0.5005.61 or later. No application-side code changes are required; this is a client-side browser vulnerability.
Chrome 102.0.5005.61 or later
- Open Chrome and navigate to Settings > Help > About Google Chrome to check the current version
- If the version is below 102.0.5005.61, click 'Update Google Chrome' to download and install the latest version
- Restart the browser after the update completes to apply the fix
- Verify the version now shows 102.0.5005.61 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
- 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-1853 — 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-1853 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