CVE-2020-6419: High severity google chrome (trace event) vulnerability
Published Apr 7, 2020
·Updated
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 Software
2 affected componentsFixes available
Google Chrome<81.0.4044.92
81.0.4044.92
Google Chrome<81.0.4044.92
Remediation
Patch Available
Event History
Apr 7, 2020
CVE Published
12:00 AM
Jun 3, 2020
CVE Published
via MITRE·10:50 PM
Data Sourced
via MITRE·10:50 PM
DescriptionWeakness
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2020-6454
- CVE-2020-6423
- CVE-2020-6455
- CVE-2020-6572
- CVE-2020-6430
- CVE-2020-6456
- CVE-2020-6431
- CVE-2020-6432
- CVE-2020-6433
- CVE-2020-6434
- CVE-2020-6435
- CVE-2020-6436
- CVE-2020-6437
- CVE-2020-6438
- CVE-2020-6439
- CVE-2020-6440
- CVE-2020-6441
- CVE-2020-6442
- CVE-2020-6443
- CVE-2020-6444
- CVE-2020-6445
- CVE-2020-6446
- CVE-2020-6447
- CVE-2020-6448
Frequently Asked Questions
1
What is the severity of CVE-2020-6419?
CVE-2020-6419 is considered a medium severity vulnerability due to its potential for exploitation that may lead to heap corruption.
2
How do I fix CVE-2020-6419?
To fix CVE-2020-6419, users should upgrade to Google Chrome version 81.0.4044.92 or later.
3
What are the consequences of exploiting CVE-2020-6419?
Exploiting CVE-2020-6419 may allow an attacker to cause a denial of service or execute arbitrary code through crafted HTML content.
4
Which versions of Google Chrome are affected by CVE-2020-6419?
CVE-2020-6419 affects all versions of Google Chrome prior to 81.0.4044.92.
5
Who is the vendor responsible for CVE-2020-6419?
The vendor responsible for CVE-2020-6419 is Google, as it pertains to their Chrome browser.