CVE-2019-5819: Incorrect escaping in developer tools
Published Jan 6, 2019
·Updated
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
Svyat Mitin
Affected Software
11 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
Apple macOS
openSUSE Backports=sle-15
openSUSE Leap=15.0
openSUSE Leap=15.1
openSUSE Leap=42.3
Fedoraproject Fedora=29
Fedoraproject Fedora=30
Debian Debian Linux=10.0
Remediation
Event History
Jan 6, 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-5819?
CVE-2019-5819 has a high severity rating due to its potential for arbitrary code execution by local attackers.
2
How do I fix CVE-2019-5819?
To address CVE-2019-5819, update Google Chrome to version 74.0.3729.108 or later.
3
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.
4
Can CVE-2019-5819 be exploited remotely?
CVE-2019-5819 requires local access for exploitation, meaning it cannot be leveraged remotely.
5
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.