dbcve.org
ChromeWeb browser · Google

CVE-2022-1855

HIGH · 8.8 CVSS v3.1 Published 2022-07-27
Fix available
A fix is available. Upgrade to 102.0.5005.61 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Use after free in Messaging in Google Chrome prior to 102.0.5005.61 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 confidence

Use-after-free vulnerability in Google Chrome's Messaging component prior to version 102.0.5005.61 allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. The vulnerability stems from improper memory management in the messaging subsystem, where memory is accessed after being freed, leading to heap corruption that can be weaponized for arbitrary code execution.

MitigationUpdate Google Chrome to version 102.0.5005.61 or later to patch the vulnerability. Organizations should deploy the update through their patch management infrastructure and verify successful installation across affected endpoints.

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
Affected:< 102.0.5005.61

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Google Chrome is installed
    Check for Chrome installation by searching for chrome.exe in typical installation paths (e.g., C:\Program Files\Google\Chrome\Application\ or C:\Program Files (x86)\Google\Chrome\Application\) or by running 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Chrome*"}' in PowerShell on Windows, or 'google-chrome --version' on Linux systems
    Affected if Google Chrome browser is found on the system
  2. Retrieve the installed Chrome version
    Open Chrome and navigate to chrome://settings/help, or run 'google-chrome --version' in terminal on Linux, or check the version property in the uninstall registry key on Windows
    Affected if Unable to determine the version indicates potential incomplete installation or non-standard deployment
  3. Compare against affected version range
    Parse the version number found and compare it numerically to 102.0.5005.61 - any version lower than 102.0.5005.61 (including 101.x, 100.x, 99.x and earlier) falls within the vulnerable range
    Affected if The installed version is less than 102.0.5005.61 (e.g., 101.0.5400.104, 100.0.4896.75, etc.)

The environment is affected if Google Chrome is installed and the running version is below 102.0.5005.61.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 102.0.5005.61 or later
Fixed in 102.0.5005.61
Interim mitigation

Update Google Chrome to version 102.0.5005.61 or later to patch the vulnerability. Organizations should deploy the update through their patch management infrastructure and verify successful installation across affected endpoints.

Recommended fix High confidence

Chrome 102.0.5005.61 or later

  1. Open Google Chrome and navigate to Settings > Help > About Google Chrome to check your current version
  2. If the version is earlier than 102.0.5005.61, Chrome will automatically check for and apply updates
  3. Restart Chrome after the update completes
  4. 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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-1855 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-1855 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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