CVE-2019-5791: Type confusion in V8
A type confusion flaw was found in the V8 component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=926651
External References:
https://chromereleases.googleblog.com/2019/03/stable-channel-update-for-desktop12.html
Other sources
Inappropriate optimization in V8 in Google Chrome prior to 73.0.3683.75 allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page.
— MITRE
Credit
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/chromium-browserto a version that resolves this vulnerability.Fixed in 73.0.3683.75 - Upgrade
Upgrade
Google Chrome (Trace Event)to a version that resolves this vulnerability.Fixed in 73.0.3683.75 - Upgrade
Upgrade
debian/chromiumto a version that resolves this vulnerability.Fixed in 150.0.7871.100-1~deb12u1Fixed in 156.0.8078.79-1~deb12u1Fixed in 150.0.7871.181-1~deb13u1Fixed in 156.0.8078.79-1~deb13u1Fixed in 156.0.8078.79-1 - Upgrade
Upgrade
Google Chrometo a version that resolves this vulnerability.Fixed in 73.0.3683.75
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2019-5791?
CVE-2019-5791 has been classified with a high severity rating due to its potential to allow remote code execution.
How do I fix CVE-2019-5791?
To fix CVE-2019-5791, update Google Chrome or Chromium Browser to version 73.0.3683.75 or later.
What types of browsers are affected by CVE-2019-5791?
CVE-2019-5791 affects Google Chrome and Chromium Browser versions prior to 73.0.3683.75.
What vulnerability does CVE-2019-5791 exploit?
CVE-2019-5791 exploits a type confusion flaw in the V8 component of the Chromium browser.
Can CVE-2019-5791 lead to data theft?
Yes, CVE-2019-5791 can potentially lead to data theft through out of bounds memory reading.