First published: Wed Jul 22 2020(Updated: )
Heap buffer overflow in history in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Credit: chrome-cve-admin@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
debian/chromium | 90.0.4430.212-1~deb10u1 116.0.5845.180-1~deb11u1 120.0.6099.129-1~deb11u1 119.0.6045.199-1~deb12u1 120.0.6099.129-1~deb12u1 120.0.6099.129-1 | |
Google Chrome | <84.0.4147.89 | |
openSUSE Backports | =15.0-sp1 | |
openSUSE Backports | =15.0-sp2 | |
Debian | =10.0 | |
Fedora | =31 | |
Fedora | =32 | |
openSUSE | =15.1 | |
openSUSE | =15.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-6517 has a high severity level due to the potential for remote exploitation through a crafted HTML page.
To fix CVE-2020-6517, upgrade to the latest version of Google Chrome or Chromium that is beyond version 84.0.4147.89.
CVE-2020-6517 exploits a heap buffer overflow vulnerability in the history component of Google Chrome.
CVE-2020-6517 affects Google Chrome versions prior to 84.0.4147.89.
There is no known workaround for CVE-2020-6517, so it is advised to update your software to mitigate the risk.