First published: Thu Aug 27 2020(Updated: )
Insufficient policy enforcement in networking in Google Chrome prior to 85.0.4183.102 allowed an attacker who convinced the user to enable logging to obtain potentially sensitive information from process memory via social engineering.
Credit: chrome-cve-admin@google.com Eric Lawrence Microsoft
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 | <85.0.4183.102 | 85.0.4183.102 |
Google Chrome | <85.0.4183.102 | |
openSUSE Backports | =15.0-sp1 | |
openSUSE Backports | =15.0-sp2 | |
openSUSE | =15.1 | |
openSUSE | =15.2 | |
Fedora | =31 | |
Fedora | =33 | |
Debian | =10.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Found alongside the following vulnerabilities)
CVE-2020-15959 has a medium severity rating due to the potential for sensitive information disclosure through social engineering.
To mitigate CVE-2020-15959, update Google Chrome to version 85.0.4183.102 or later.
CVE-2020-15959 affects Google Chrome versions before 85.0.4183.102.
CVE-2020-15959 requires user interaction to enable logging, making it a social engineering exploit rather than a direct remote attack.
Yes, CVE-2020-15959 is applicable to multiple Linux distributions that use affected versions of Google Chrome.