CVE-2019-5819: Incorrect escaping in developer tools
Insufficient data validation in developer tools in Google Chrome on OS X prior to 74.0.3729.108 allowed a local attacker to execute arbitrary code via a crafted string copied to clipboard.
Credit
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Google Chrome (Trace Event)to a version that resolves this vulnerability.Fixed in 74.0.3729.108 - Upgrade
Upgrade
debian/chromiumto a version that resolves this vulnerability.Fixed in 150.0.7871.100-1~deb12u1Fixed in 156.0.8078.73-1~deb12u1Fixed in 150.0.7871.181-1~deb13u1Fixed in 156.0.8078.73-1~deb13u1Fixed in 156.0.8078.47-1Fixed in 156.0.8078.79-1
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2019-5819?
CVE-2019-5819 has a high severity rating due to its potential for arbitrary code execution by local attackers.
How do I fix CVE-2019-5819?
To address CVE-2019-5819, update Google Chrome to version 74.0.3729.108 or later.
Which versions of Chrome are affected by CVE-2019-5819?
CVE-2019-5819 affects all versions of Google Chrome prior to 74.0.3729.108.
Can CVE-2019-5819 be exploited remotely?
CVE-2019-5819 requires local access for exploitation, meaning it cannot be leveraged remotely.
Is there a patch available for CVE-2019-5819?
Yes, Google has released patches for CVE-2019-5819 in version 74.0.3729.108 and subsequent updates.