DIESER SERVICE KANN ÜBERSETZUNGEN VON GOOGLE ENTHALTEN. GOOGLE ÜBERNIMMT KEINERLEI VERANTWORTUNG FÜR DIE ÜBERSETZUNGEN. DARUNTER FÄLLT JEGLICHE VERANTWORTUNG IN BEZUG AUF RICHTIGKEIT UND ZUVERLÄSSIGKEIT SOWIE JEGLICHE STILLSCHWEIGENDEN GEWÄHRLEISTUNGEN DER MARKTGÄNGIGKEIT, NICHT-VERLETZUNG VON RECHTEN DRITTER ODER DER EIGNUNG FÜR EINEN BESTIMMTEN ZWECK.

Die Website von Kaspersky Lab wurde für Ihre Bequemlichkeit mithilfe einer Übersetzungssoftware von Google Translate übersetzt. Es wurden angemessene Bemühungen für die Bereitstellung einer akkuraten Übersetzung unternommen. Bitte beachten Sie, dass automatisierte Übersetzungen nicht perfekt sind und menschliche Übersetzer in keinem Fall ersetzen sollen. Übersetzungen werden den Nutzern der Kaspersky-Lab-Website als Service und "wie sie sind" zur Verfügung gestellt. Die Richtigkeit, Zuverlässigkeit oder Korrektheit jeglicher Übersetzungen aus dem Englischen in eine andere Sprache wird weder ausdrücklich noch stillschweigend garantiert. Einige Inhalte (z. B. Bilder, Videos, Flash, usw.) können aufgrund der Einschränkungen der Übersetzungssoftware möglicherweise nicht inhaltsgetreu übersetzt werden.

KLA10655
Multiple vulnerabilities in Google Chrome
Aktualisiert: 03/29/2019
Erkennungsdatum
?
09/01/2015
Schweregrad
?
Kritisch
Beschreibung

Multiple serious vulnerabilities have been found in Google Chrome. Malicious users can exploit these vulnerabilities to spoof user interface, cause denial of service, bypass security restrictions or obtain sensitive information.

Below is a complete list of vulnerabilities

  1. Lack of content restrictions at hosted app’s window can be exploited remotely via a specially designed app to spoof user interface;
  2. Lack of data verification at Blink can be exploited remotely via a specially designed web site to cause denial of service;
  3. Double free vulnerability at PDFium can be exploited remotely to cause denial of service;
  4. Multiple unspecified vulnerabilities can be exploited remotely to cause denial of service or possibly conduct other impact;
  5. Improper IFRAME restrictions at Blink can be exploited remotely via a specially designed JavaScript to obtain sensitive information;
  6. Use-after-free vulnerability at Blink can be exploited remotely via timer manipulations to cause denial of service;
  7. Lack of URL restrictions at extension uninstaller can be exploited remotely via a specially designed extension to access arbitrary URL;
  8. Improper request source consideration at WebRequest API can be exploited remotely via a specially designed app or extension to bypass security restrictions;
  9. Lack of characters display restrictions can be exploited remotely via a specially designed URL to spoof user interface;
  10. Multiple use-after-free vulnerabilities at PrintWebViewHelper can be exploited remotely via a specially designed IPC messages to cause denial of service;
  11. Lack of data verification at Skia can be exploited remotely to cause denial of service;
  12. An unknown vulnerability at Blink can be exploited remotely to bypass security restrictions;
  13. Lack of restrictions at Blink can be exploited remotely via a specially designed web site to bypass security restrictions.

Technical details

(1) caused by hiding location bar for a hosted app’s window after navigation away from installation site.

Decompose function in Blink does not verify success of matrix inversion operation. Unitialized memory access and application crash can be caused by using (2)

(3) related to OpenJPEG before r3002.

(5) caused by lack of restrictions in availability of IFRAME Resource Timing API. Can be exploited via a specially designed JavaScript code that cause history.back call.

Vulnerability (6) can be exploited via shared-timer erroneous firing.

When extension uninstalled Chrome does not ensure that preference setUninstallURL corresponds to web site with proper functionality. (7) can be exploited to access arbitrary URL after specially designed application uninstallation.

Vulnerability (9) have some requisitions to be exploited. As Chrome does not restricts display of Unicide LOCK symbol attacker can spoof SSL lock icon by placing special symbol at end of URL at localizations with right-to-left languages.

(10) can be exploited via nested IPC messages during preparation for printing.

(11) can be exploited via matrix element which causes infinite result during calculation of inversion.

Exploitation of (12) leads to bypass Same Origin policy.

(13) caused by lack of check if DOM node is expected and leads to bypassing Same Origin Policy via DOM tree corruption.

Beeinträchtigte Produkte

Google Chrome versions earlier than 45.0.2454.85

Lösung

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.
Get Google Chrome

Ursprüngliche Informationshinweise

Google release blog entry

Folgen
?
OSI 
[?]

DoS 
[?]

SB 
[?]

SUI 
[?]
CVE-IDS
?
CVE-2015-12997.5Critical
CVE-2015-13005.0Critical
CVE-2015-13017.5Critical
CVE-2015-65817.5Critical
CVE-2015-12957.5Critical
CVE-2015-12965.0Critical
CVE-2015-12977.5Critical
CVE-2015-12984.3Critical
CVE-2015-65826.8Critical
CVE-2015-65834.3Critical
CVE-2015-65807.5Critical
CVE-2015-12947.5Critical
CVE-2015-12916.4Critical
CVE-2015-12925.0Critical
CVE-2015-12937.5Critical

Link zum Original