CVE-2022-3723
Google Chromium V8 Type Confusion
- Published1 Nov 2022
- Added to CISA KEV28 Oct 2022
- Remediation due18 Nov 2022
Description
Type confusion in V8 in Google Chrome prior to 107.0.5304.87 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2022-3723 being actively exploited?
Yes. CVE-2022-3723 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 28 Oct 2022.
How severe is CVE-2022-3723?
CVE-2022-3723 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 7.92% probability of exploitation.
Which products are affected by CVE-2022-3723?
Affected products include Google Chrome.
How do I fix CVE-2022-3723?
Upgrade affected software to a fixed version, for example Google Chrome 107.0.5304.87 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2022-3723 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, a risk for it never ranks below high, and the update that fixes it moves to the Emergency patch lane. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.