CVE-2019-5818: Uninitialized value in media reader
Published Feb 8, 2019
·Updated
Uninitialized data in media in Google Chrome prior to 74.0.3729.108 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted video file.
Credit
Adrian Tolbaru
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
openSUSE Backports=sle-15
openSUSE Leap=15.0
openSUSE Leap=15.1
openSUSE Leap=42.3
Debian Debian Linux=10.0
Fedoraproject Fedora=29
Fedoraproject Fedora=30
Remediation
Event History
Feb 8, 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-5818?
CVE-2019-5818 has been classified as a medium severity vulnerability.
2
How do I fix CVE-2019-5818?
To fix CVE-2019-5818, upgrade Google Chrome to version 74.0.3729.108 or later.
3
What happens if I don't address CVE-2019-5818?
If CVE-2019-5818 is not addressed, attackers may exploit the vulnerability to access potentially sensitive information from process memory.
4
Which versions of Google Chrome are affected by CVE-2019-5818?
CVE-2019-5818 affects Google Chrome versions prior to 74.0.3729.108.
5
Is CVE-2019-5818 specific to Google Chrome only?
Yes, CVE-2019-5818 is specifically a vulnerability found in Google Chrome.