CVE-2019-5807: Memory corruption in V8
Published Mar 26, 2019
·Updated
Object lifetime issue in V8 in Google Chrome prior to 74.0.3729.108 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Credit
TimGMichaud(Leviathan Security Group)
Affected Software
10 affected componentsFixes available
debian/chromium
90.0.4430.212-1~deb10u1116.0.5845.180-1~deb11u1120.0.6099.129-1~deb11u1119.0.6045.199-1~deb12u1120.0.6099.129-1~deb12u1120.0.6099.129-1
Google Chrome<74.0.3729.108
74.0.3729.108
Google Chrome<74.0.3729.108
Debian Debian Linux=10.0
Fedoraproject Fedora=29
Fedoraproject Fedora=30
openSUSE Backports=sle-15
openSUSE Leap=15.0
openSUSE Leap=15.1
openSUSE Leap=42.3
Event History
Mar 26, 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-5807?
CVE-2019-5807 is classified as a high-severity vulnerability that can lead to heap corruption in Google Chrome.
2
How do I fix CVE-2019-5807?
To fix CVE-2019-5807, update Google Chrome to version 74.0.3729.108 or later.
3
Which versions of Google Chrome are affected by CVE-2019-5807?
CVE-2019-5807 affects all versions of Google Chrome prior to 74.0.3729.108.
4
Does CVE-2019-5807 affect Chromium on Debian?
Yes, CVE-2019-5807 affects certain versions of Chromium on Debian that are lower than 74.0.3729.108.
5
What platforms are impacted by CVE-2019-5807?
CVE-2019-5807 impacts Google Chrome, Chromium on Debian, and various versions of Fedora and openSUSE.