CVE-2019-5816: High severity google chrome (trace event) vulnerability
Published Mar 10, 2019
·Updated
Process lifetime issue in Chrome in Google Chrome on Android prior to 74.0.3729.108 allowed a remote attacker to potentially persist an exploited process via a crafted HTML page.
Credit
Yongke Wang(Tencent's Xuanwu Lab)
Affected Software
8 affected componentsFixes available
Google Chrome<74.0.3729.108
74.0.3729.108
Google Chrome<74.0.3729.108
Google Android
Fedoraproject Fedora=29
openSUSE Backports=sle-15
openSUSE Leap=15.0
openSUSE Leap=15.1
openSUSE Leap=42.3
Remediation
Patch Available
Event History
Mar 10, 2019
CVE Published
12:00 AM
Jun 27, 2019
CVE Published
via MITRE·04:13 PM
Data Sourced
via MITRE·04:13 PM
DescriptionWeakness
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
1
What is the severity of CVE-2019-5816?
CVE-2019-5816 has been classified as a high severity vulnerability.
2
How do I fix CVE-2019-5816?
To fix CVE-2019-5816, upgrade Google Chrome to version 74.0.3729.108 or later.
3
What systems are affected by CVE-2019-5816?
CVE-2019-5816 affects Google Chrome on Android versions prior to 74.0.3729.108.
4
What type of attack does CVE-2019-5816 involve?
CVE-2019-5816 involves a remote attacker potentially exploiting a crafted HTML page.
5
Can CVE-2019-5816 cause persistent exploitation?
Yes, CVE-2019-5816 can potentially allow an exploited process to persist.