CVE-2019-5765: Medium severity google chrome vulnerability

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

Other sources

An insufficient policy enforcement flaw was found in the the browser component of the Chromium browser.

Upstream bug(s):

https://code.google.com/p/chromium/issues/detail?id=922627

External References:

https://chromereleases.googleblog.com/2019/01/stable-channel-update-for-desktop.html

Red Hat

Affected Software

12 affected componentsFixes available
debian/chromium
90.0.4430.212-1~deb10u1116.0.5845.180-1~deb11u1118.0.5993.70-1~deb11u1116.0.5845.180-1~deb12u1118.0.5993.70-1~deb12u1118.0.5993.70-1
redhat/chromium-browser<72.0.3626.81
72.0.3626.81
All of the following
Google Chrome<72.0.3626.81
Google Android
redhat Enterprise Linux Desktop=6.0
redhat Enterprise Linux Server=6.0
redhat Enterprise Linux Workstation=6.0
Debian Debian Linux=9.0
Fedoraproject Fedora=29
Fedoraproject Fedora=30
Google Chrome<72.0.3626.81
Google Android

Event History

Feb 19, 2019
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
DescriptionWeakness
Data Sourced
via NVD·05:29 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2019-5765?

CVE-2019-5765 has a high severity rating due to its potential to expose sensitive information.

2

How do I fix CVE-2019-5765?

To fix CVE-2019-5765, update Google Chrome to version 72.0.3626.81 or later.

3

Which software versions are affected by CVE-2019-5765?

CVE-2019-5765 affects Google Chrome versions prior to 72.0.3626.81 and various distributions of Chromium.

4

Can CVE-2019-5765 be exploited remotely?

CVE-2019-5765 is not remotely exploitable; it requires local access to the device.

5

Is there a workaround for CVE-2019-5765?

There is no specific workaround for CVE-2019-5765, and upgrading is the recommended solution.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203