logo
DATABASE RESOURCES PRICING ABOUT US

KLA11152 Multiple vulnerabilities in Google Chrome

Description

### *Detect date*: 12/07/2017 ### *Severity*: Critical ### *Description*: Multiple serious vulnerabilities have been found in Google Chrome. Malicious users can exploit these vulnerabilities to cause denial of service, obtain sensitive information, spoof user interface, bypass security restrictions and possibly to execute arbitrary code. ### *Affected products*: Google Chrome versions earlier than 63.0.3239.84 ### *Solution*: Update to the latest version. File with name old_chrome can be still detected after update. It caused by Google Chrome update policy which does not remove old versions when installing updates. Try to contact vendor for further delete instructions or ignore such kind of alerts at your own risk. [Download Google Chrome](<https://www.google.com/chrome/browser/desktop/>) ### *Original advisories*: [Stable Channel Update for Desktop](<https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html>) ### *Impacts*: ACE ### *Related products*: [Google Chrome](<https://threats.kaspersky.com/en/product/Google-Chrome/>) ### *CVE-IDS*: [CVE-2017-15422](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15422>)4.3Warning [CVE-2017-15423](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15423>)5.0Critical [CVE-2017-15424](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15424>)4.3Warning [CVE-2017-15425](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15425>)4.3Warning [CVE-2017-15426](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15426>)4.3Warning [CVE-2017-15427](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15427>)4.3Warning [CVE-2017-15407](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15407>)6.8High [CVE-2017-15408](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15408>)6.8High [CVE-2017-15409](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15409>)6.8High [CVE-2017-15410](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15410>)6.8High [CVE-2017-15411](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15411>)6.8High [CVE-2017-15412](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15412>)6.8High [CVE-2017-15413](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15413>)6.8High [CVE-2017-15415](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15415>)4.3Warning [CVE-2017-15416](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15416>)4.3Warning [CVE-2017-15417](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15417>)2.6Warning [CVE-2017-15418](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15418>)4.3Warning [CVE-2017-15419](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15419>)4.3Warning [CVE-2017-15420](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15420>)4.3Warning


Related