CVE-2020-6419
published 2020-06-03CVE-2020-6419: Out of bounds write in V8 in Google Chrome prior to 81.0.4044.92 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
PriorityP341high8.8CVSS 3.1
AVNACLPRNUIRSUCHIHAH
EPSS
0.75%
51.2th percentile
Out of bounds write in V8 in Google Chrome prior to 81.0.4044.92 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Affected
8 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| chromium | chromium | >= 0 < 81.0.4044.92-1 | 81.0.4044.92-1 |
| chromium | chromium | >= 0 < 81.0.4044.92-1 | 81.0.4044.92-1 |
| chromium | chromium | >= 0 < 81.0.4044.92-1 | 81.0.4044.92-1 |
| chromium | chromium | >= 0 < 81.0.4044.92-1 | 81.0.4044.92-1 |
| debian | chromium | < chromium 81.0.4044.92-1 (bookworm) | chromium 81.0.4044.92-1 (bookworm) |
| chrome | < 81.0.4044.92 | 81.0.4044.92 | |
| chrome | >= unspecified < 81.0.4044.92 | 81.0.4044.92 | |
| chrome_chrome | — | — |
CVSS provenance
nvdv3.18.8HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvdv2.06.8MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:P
osv8.8HIGH
vendor_debian8.8HIGH
vendor_redhat8.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
chromium-browser: Out of bounds read and write in V8
vendor_redhat·2020-04-07·CVSS 8.8
CVE-2020-6419 [HIGH] CWE-125 chromium-browser: Out of bounds read and write in V8
chromium-browser: Out of bounds read and write in V8
Out of bounds write in V8 in Google Chrome prior to 81.0.4044.92 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Chrome
Stable Channel Update for Desktop: CVE-2020-6455
vendor_chrome·2020-04-07·CVSS 8.8
CVE-2020-6455 [HIGH] Stable Channel Update for Desktop: CVE-2020-6455
Stable Channel Update for Desktop
CVE-2020-6455: Out of bounds read in WebSQL. Reported by Nan Wang(@eternalsakura13) and Guang Gong of Alpha Lab, Qihoo 360 on 2020-03-09
[$2000][ 1040325 ] High CVE-2020-6419: Out of bounds read and write in V8
Reported by David Manouchehri on 2020-01-09 [$N/A] [ 1066893 ] High CVE-2020-6572: Use after free in media
Severity: high
Debian
CVE-2020-6419: chromium - Out of bounds write in V8 in Google Chrome prior to 81.0.4044.92 allowed a remot...
vendor_debian·2020·CVSS 8.8
CVE-2020-6419 [HIGH] CVE-2020-6419: chromium - Out of bounds write in V8 in Google Chrome prior to 81.0.4044.92 allowed a remot...
Out of bounds write in V8 in Google Chrome prior to 81.0.4044.92 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Scope: local
bookworm: resolved (fixed in 81.0.4044.92-1)
bullseye: resolved (fixed in 81.0.4044.92-1)
forky: resolved (fixed in 81.0.4044.92-1)
sid: resolved (fixed in 81.0.4044.92-1)
trixie: resolved (fixed in 81.0.4044.92-1)
GHSA
GHSA-2qg4-m4gf-w255: Out of bounds write in V8 in Google Chrome prior to 81
ghsa_unreviewed·2022-05-24
CVE-2020-6419 [MEDIUM] GHSA-2qg4-m4gf-w255: Out of bounds write in V8 in Google Chrome prior to 81
Out of bounds write in V8 in Google Chrome prior to 81.0.4044.92 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
OSV
CVE-2020-6419: Out of bounds write in V8 in Google Chrome prior to 81
osv·2020-06-03·CVSS 8.8
CVE-2020-6419 [HIGH] CVE-2020-6419: Out of bounds write in V8 in Google Chrome prior to 81
Out of bounds write in V8 in Google Chrome prior to 81.0.4044.92 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2020-6419 chromium: chromium-browser: Out of bounds read and write in V8 [fedora-all]
bugzilla·2020-06-05·CVSS 8.8
CVE-2020-6419 [HIGH] CVE-2020-6419 chromium: chromium-browser: Out of bounds read and write in V8 [fedora-all]
CVE-2020-6419 chromium: chromium-browser: Out of bounds read and write in V8 [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple suppor
Bugzilla
CVE-2020-6419 chromium-browser: Out of bounds read and write in V8
bugzilla·2020-06-05·CVSS 8.8
CVE-2020-6419 [HIGH] CVE-2020-6419 chromium-browser: Out of bounds read and write in V8
CVE-2020-6419 chromium-browser: Out of bounds read and write in V8
An out of bounds read and write flaw was found in the V8 component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=1040325
External References:
https://chromereleases.googleblog.com/2020/04/stable-channel-update-for-desktop_7.html
Discussion:
Created chromium tracking bugs for this issue:
Affects: epel-all [bug 1844463]
Affects: fedora-all [bug 1844462]
---
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):
https://access.redhat.com/security/cve/cve-2020-6419
Bugzilla
CVE-2020-6419 chromium: chromium-browser: Out of bounds read and write in V8 [epel-all]
bugzilla·2020-06-05·CVSS 8.8
CVE-2020-6419 [HIGH] CVE-2020-6419 chromium: chromium-browser: Out of bounds read and write in V8 [epel-all]
CVE-2020-6419 chromium: chromium-browser: Out of bounds read and write in V8 [epel-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported
2020-06-03
Published