8579594118646068818: Google chrome (trace event) vulnerability
Published Feb 4, 2020
·Updated
Affected Software
1 affected componentFixes available
Google Chrome<80.0.3987.87
80.0.3987.87
Event History
Feb 4, 2020
Advisory Published
via Google·12:00 AM
Child vulnerabilities
Contains the following vulnerabilities.
- CVE-2020-6381
- CVE-2020-6382
- CVE-2019-18197
- CVE-2019-19926
- CVE-2020-6385
- CVE-2019-19880
- CVE-2019-19925
- CVE-2020-6387
- CVE-2020-6388
- CVE-2020-6389
- CVE-2020-6390
- CVE-2020-6391
- CVE-2020-6392
- CVE-2020-6393
- CVE-2020-6499
- CVE-2020-6394
- CVE-2020-6395
- CVE-2020-6396
- CVE-2020-6397
- CVE-2020-6398
- CVE-2020-6399
- CVE-2020-6500
- CVE-2020-6400
- CVE-2020-6401
- CVE-2020-6402
- CVE-2020-6501
- CVE-2020-6403
- CVE-2020-6404
- CVE-2020-6405
- CVE-2020-6406
- CVE-2019-19923
- CVE-2020-6408
- CVE-2020-6409
- CVE-2020-6410
- CVE-2020-6411
- CVE-2020-6502
- CVE-2020-6412
- CVE-2020-6413
- CVE-2020-6414
- CVE-2020-6415
- CVE-2020-6416
- CVE-2020-6417
Frequently Asked Questions
1
What is the severity of vulnerability 8579594118646068818?
The severity of vulnerability 8579594118646068818 is rated as 23, indicating a significant risk.
2
How do I fix vulnerability 8579594118646068818?
To fix vulnerability 8579594118646068818, ensure that you are using the latest version of Google Chrome as released on February 4, 2020.
3
What is the impact of vulnerability 8579594118646068818?
The impact of vulnerability 8579594118646068818 may include potential arbitrary code execution, which poses a risk to user data and application integrity.
4
Who is affected by vulnerability 8579594118646068818?
Users of Google Chrome prior to the update released on February 4, 2020, are affected by vulnerability 8579594118646068818.
5
Is there a workaround for vulnerability 8579594118646068818?
There is no specific workaround for vulnerability 8579594118646068818; the recommended action is to upgrade to the latest version of Google Chrome.