CVE-2020-6419

Reference Links

• https://chromereleases.googleblog.com/2020/04/stable-channel-update-for-desktop_7.html (Advisory)
• https://crbug.com/1040325

Parent vulnerabilities

(Appears in the following advisories)

• 4697812152063391612

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

• 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.

• 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.

• 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.

• 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.

• 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.