dbcve.org
ChromeWeb browser · Google

CVE-2022-1143

HIGH · 8.8 CVSS v3.1 Published 2022-07-23
Fix available
A fix is available. Upgrade to 100.0.4896.60 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
Heap buffer overflow in WebUI in Google Chrome prior to 100.0.4896.60 allowed a remote attacker who convinced a user to engage in specific user interaction to potentially exploit heap corruption via specific input into DevTools.

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 confidence

Heap buffer overflow vulnerability in Chrome's WebUI component allows a remote attacker who tricks a user into specific interactions to corrupt heap memory via malicious input into DevTools.

MitigationUpdate Google Chrome to version 100.0.4896.60 or later to obtain the vendor patch.

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:< 100.0.4896.60

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. Check installed Chrome version
    Navigate to chrome://settings/help in the Chrome browser, or click Help > About Google Chrome in the menu
    Affected if The version displayed is less than 100.0.4896.60 (for example, 99.0.x.x or earlier)
  2. Verify Chrome is the affected browser
    Confirm the browser is Google Chrome, not Chromium or a Chromium-based browser (Edge, Brave, etc.)
    Affected if The browser is Google Chrome and the version is below 100.0.4896.60
  3. Confirm DevTools access is available
    Open DevTools by pressing F12, Ctrl+Shift+I, or right-clicking and selecting Inspect - no special configuration should be required
    Affected if DevTools can be opened, as the vulnerability requires malicious input into DevTools

You are affected if you are running Google Chrome version below 100.0.4896.60 and have standard DevTools access available in your browser

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 100.0.4896.60 or later
Fixed in 100.0.4896.60
Interim mitigation

Update Google Chrome to version 100.0.4896.60 or later to obtain the vendor patch.

Recommended fix High confidence

Chrome 100.0.4896.60 or later

  1. Check current Chrome version by navigating to chrome://settings/help
  2. Update Chrome to version 100.0.4896.60 or later by clicking 'Update Google Chrome' (or use the menu: Help > About Google Chrome)
  3. Restart Chrome after the update completes
Caveat Routine major version update; may require re-validation of critical web applications and extensions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get the upgrade done

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

Check whether your project pulls in CVE-2022-1143 — 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-1143 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