First published: Wed Jan 30 2019(Updated: )
An exposed debugging endpoint in the browser in Google Chrome on Android prior to 72.0.3626.81 allowed a local attacker to obtain potentially sensitive information from process memory via a crafted Intent.
Credit: cve-coordination@google.com 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 118.0.5993.70-1~deb11u1 116.0.5845.180-1~deb12u1 118.0.5993.70-1~deb12u1 118.0.5993.70-1 | |
redhat/chromium-browser | <72.0.3626.81 | 72.0.3626.81 |
All of | ||
Google Chrome (Trace Event) | <72.0.3626.81 | |
Android | ||
Red Hat Enterprise Linux Desktop | =6.0 | |
Red Hat Enterprise Linux Server | =6.0 | |
Red Hat Enterprise Linux Workstation | =6.0 | |
Debian | =9.0 | |
Fedora | =29 | |
Fedora | =30 | |
Google Chrome (Trace Event) | <72.0.3626.81 | |
Android |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-5765 has a high severity rating due to its potential to expose sensitive information.
To fix CVE-2019-5765, update Google Chrome to version 72.0.3626.81 or later.
CVE-2019-5765 affects Google Chrome versions prior to 72.0.3626.81 and various distributions of Chromium.
CVE-2019-5765 is not remotely exploitable; it requires local access to the device.
There is no specific workaround for CVE-2019-5765, and upgrading is the recommended solution.