CVE-2022-3723 kev in the critical feed json
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…
published 4y ago modified 4mo ago also EUVD-2022-43079
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Exploited
- added 2022-10-28
- epss
- 7.9%
- EPSS 7.9% chance of exploitation in 30 days, percentile 94%
- public exploits
- 0
- none known
Summary
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)
Patch / fix
cisa required action Apply updates per vendor instructions.
- Google Chrome 107.0.5304.87
- chromium Debian 14, Debian 13, Debian 12 107.0.5304.87-1
debian advisories DEBIAN-CVE-2022-3723
- chromium-browser Ubuntu 18.04 LTS 107.0.5304.87-0ubuntu11.18.04.1
ubuntu advisories UBUNTU-CVE-2022-3723
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- chromium openSUSE Tumbleweed 107.0.5304.87-1.1
- chromium openSUSE Tumbleweed 113.0.5672.92-1.1
- opera openSUSE Leap 15.5 NonFree 99.0.4788.13-lp155.3.6.1
- opera openSUSE Leap 15.4 NonFree 93.0.4585.11-lp154.2.29.1
- opera openSUSE Leap 15.3 NonFree 93.0.4585.11-lp153.2.69.1
- chromium Package Hub 15 SP4, openSUSE Leap 15.4 107.0.5304.87-bp154.2.40.1
- chromium Package Hub 15 SP3, openSUSE Leap 15.3 107.0.5304.87-bp153.2.133.1
opensuse advisories openSUSE-SU-2024:12460-1openSUSE-SU-2024:12948-1openSUSE-SU-2023:0115-1openSUSE-SU-2022:10219-1openSUSE-SU-2022:10218-1openSUSE-SU-2022:10180-1
Is CVE-2022-3723 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-3723 updated cvss 8.8
chromium-browser: Type Confusion in V8
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Timeline
- Found exploited as a 0-day (Project Zero)
- 0-day patched (Project Zero)
- Added to CISA KEV
- Published
- CISA patch deadline
- CISA SSVC: exploitation active
Known exploited
- Added
- 4y ago
- Patch by
- 2022-11-18 (3y ago)
- Ransomware
- Not known
- Required action
- Apply updates per vendor instructions.
- Vendor, product
- Google, Chromium V8
- CISA name
- Google Chromium V8 Type Confusion Vulnerability
Zero-day
Detected in real attacks while still unknown to the vendor and the public, per Google Project Zero's 0day In-the-Wild tracker.
- Found
- 2022-10-25
- Patched
- 2022-10-27
- Details
- project zero root cause analysis
CISA SSVC
- Exploitation
- Active, exploited in the wild
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
7.92% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- Google Chrome
Classification
- Weakness
-
- CWE-843 Access of Resource Using Incompatible Type
- Technology feeds
References
-
security.gentoo.org
/glsa/202305-10
vendor-advisory, third-party-advisory
-
chromereleases.googleblog.com
/2022/10/stable-channel-update-for-desktop_27.html
release-notes, vendor-advisory
-
crbug.com
/1378239
permissions-required
-
cisa.gov
/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-3723
government-resource, us-government-resource
Sources
- CVE List CVE-2022-3723
- NVD CVE-2022-3723
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.