First published: Fri Feb 08 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: cve-coordination@google.com Adrian Tolbaru
Affected Software | Affected Version | How to fix |
---|---|---|
debian/chromium | 90.0.4430.212-1~deb10u1 116.0.5845.180-1~deb11u1 120.0.6099.129-1~deb11u1 119.0.6045.199-1~deb12u1 120.0.6099.129-1~deb12u1 120.0.6099.129-1 | |
Google Chrome (Trace Event) | <74.0.3729.108 | 74.0.3729.108 |
Google Chrome | <74.0.3729.108 | |
SUSE Backports | =sle-15 | |
SUSE Linux | =15.0 | |
SUSE Linux | =15.1 | |
SUSE Linux | =42.3 | |
Debian Linux | =10.0 | |
Red Hat Fedora | =29 | |
Red Hat Fedora | =30 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Found alongside the following vulnerabilities)
CVE-2019-5818 has been classified as a medium severity vulnerability.
To fix CVE-2019-5818, upgrade Google Chrome to version 74.0.3729.108 or later.
If CVE-2019-5818 is not addressed, attackers may exploit the vulnerability to access potentially sensitive information from process memory.
CVE-2019-5818 affects Google Chrome versions prior to 74.0.3729.108.
Yes, CVE-2019-5818 is specifically a vulnerability found in Google Chrome.