CVE-2022-2415 json
Heap buffer overflow in WebGL in Google Chrome prior to 103.0.5060.53 allowed a remote attacker to potentially exploit heap corruption via…
published 4y ago modified 4mo ago also EUVD-2022-34678
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
Heap buffer overflow in WebGL in Google Chrome prior to 103.0.5060.53 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Patch / fix
- Google Chrome 103.0.5060.53
- chromium Debian 14, Debian 13, Debian 12 103.0.5060.53-1
debian advisories DEBIAN-CVE-2022-2415
- chromium-browser Ubuntu 18.04 LTS 103.0.5060.134-0ubuntu0.18.04.1
ubuntu advisories UBUNTU-CVE-2022-2415
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
Is CVE-2022-2415 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 FencerExploit prediction
1.98% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 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-787 Out-of-bounds Write
- Technology feeds
References
-
chromereleases.googleblog.com
/2022/06/stable-channel-update-for-desktop_21.html
release-notes, vendor-advisory
-
crbug.com
/1316368
permissions-required, vendor-advisory
-
packetstormsecurity.com
/files/167972/Chrome-WebGL-Uniform-Integer-Overflows.html
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2022-2415
- NVD CVE-2022-2415
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.