What is the severity of CVE-2022-1143?

CVE-2022-1143 is classified as a high-severity vulnerability due to its potential for remote exploitation.

How do I fix CVE-2022-1143?

To fix CVE-2022-1143, upgrade Google Chrome to version 100.0.4896.60 or later.

What impact does CVE-2022-1143 have on users?

CVE-2022-1143 may allow a remote attacker to exploit heap corruption via user interaction with DevTools.

Which versions of Google Chrome are affected by CVE-2022-1143?

Google Chrome versions prior to 100.0.4896.60 are affected by CVE-2022-1143.

Is there a workaround for CVE-2022-1143?

There are no known workarounds for CVE-2022-1143; updating is the recommended action.

Vulnerability/
CVE-2022-1143

high

8.8

CWE

787 119

7/3/2022

22/7/2022

2/8/2024

CVE-2022-1143: Heap buffer overflow in WebUI

First published: Mon Mar 07 2022(Updated: )

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.

Credit: chrome-cve-admin@google.com Leecraso 360 Alpha LabGuang Gong 360 Alpha Lab

Affected Software	Affected Version	How to fix
Google Chrome	<100.0.4896.60
Google Chrome	<100.0.4896.60	100.0.4896.60

Never miss a vulnerability like this again

Reference Links

Parent vulnerabilities

(Appears in the following advisories)

3952572103814780022

Peer vulnerabilities

(Found alongside the following vulnerabilities)

Frequently Asked Questions

What is the severity of CVE-2022-1143?
CVE-2022-1143 is classified as a high-severity vulnerability due to its potential for remote exploitation.
How do I fix CVE-2022-1143?
To fix CVE-2022-1143, upgrade Google Chrome to version 100.0.4896.60 or later.
What impact does CVE-2022-1143 have on users?
CVE-2022-1143 may allow a remote attacker to exploit heap corruption via user interaction with DevTools.
Which versions of Google Chrome are affected by CVE-2022-1143?
Google Chrome versions prior to 100.0.4896.60 are affected by CVE-2022-1143.
Is there a workaround for CVE-2022-1143?
There are no known workarounds for CVE-2022-1143; updating is the recommended action.

agent/type
collector/nvd-index
agent/software-canonical-lookup-request
agent/weakness
agent/references
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
collector/chrome-releases
agent/software-canonical-lookup
agent/author
agent/title
agent/severity
agent/softwarecombine
agent/event
agent/first-publish-date
agent/trending
agent/tags
agent/source
vendor/google
canonical/google chrome

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2022-1143?
CVE-2022-1143 is classified as a high-severity vulnerability due to its potential for remote exploitation.
How do I fix CVE-2022-1143?
To fix CVE-2022-1143, upgrade Google Chrome to version 100.0.4896.60 or later.
What impact does CVE-2022-1143 have on users?
CVE-2022-1143 may allow a remote attacker to exploit heap corruption via user interaction with DevTools.
Which versions of Google Chrome are affected by CVE-2022-1143?
Google Chrome versions prior to 100.0.4896.60 are affected by CVE-2022-1143.
Is there a workaround for CVE-2022-1143?
There are no known workarounds for CVE-2022-1143; updating is the recommended action.