Summary
This update for Chromium to version 72.0.3626.96 fixes the following issues:
Security issues fixed (bsc#1123641 and bsc#1124936):
- CVE-2019-5784: Inappropriate implementation in V8
- CVE-2019-5754: Inappropriate implementation in QUIC Networking.
- CVE-2019-5782: Inappropriate implementation in V8.
- CVE-2019-5755: Inappropriate implementation in V8.
- CVE-2019-5756: Use after free in PDFium.
- CVE-2019-5757: Type Confusion in SVG.
- CVE-2019-5758: Use after free in Blink.
- CVE-2019-5759: Use after free in HTML select elements.
- CVE-2019-5760: Use after free in WebRTC.
- CVE-2019-5761: Use after free in SwiftShader.
- CVE-2019-5762: Use after free in PDFium.
- CVE-2019-5763: Insufficient validation of untrusted input in V8.
- CVE-2019-5764: Use after free in WebRTC.
- CVE-2019-5765: Insufficient policy enforcement in the browser.
- CVE-2019-5766: Insufficient policy enforcement in Canvas.
- CVE-2019-5767: Incorrect security UI in WebAPKs.
- CVE-2019-5768: Insufficient policy enforcement in DevTools.
- CVE-2019-5769: Insufficient validation of untrusted input in Blink.
- CVE-2019-5770: Heap buffer overflow in WebGL.
- CVE-2019-5771: Heap buffer overflow in SwiftShader.
- CVE-2019-5772: Use after free in PDFium.
- CVE-2019-5773: Insufficient data validation in IndexedDB.
- CVE-2019-5774: Insufficient validation of untrusted input in SafeBrowsing.
- CVE-2019-5775: Insufficient policy enforcement in Omnibox.
- CVE-2019-5776: Insufficient policy enforcement in Omnibox.
- CVE-2019-5777: Insufficient policy enforcement in Omnibox.
- CVE-2019-5778: Insufficient policy enforcement in Extensions.
- CVE-2019-5779: Insufficient policy enforcement in ServiceWorker.
- CVE-2019-5780: Insufficient policy enforcement.
- CVE-2019-5781: Insufficient policy enforcement in Omnibox.
For a full list of changes refer to https://chromereleases.googleblog.com/2019/02/stable-channel-update-for-desktop.html
This update was imported from the openSUSE:Leap:15.0:Update update project.
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| SUSE · Package Hub 15 | chromium | 72.0.3626.96-bp150.2.32.1 |
Vulnerabilities 30
-
Unscored —
Implementation error in QUIC Networking in Google Chrome prior to 72.0.3626.81 allowed an attacker running or able to c…
-
Unscored —
Incorrect handling of negative zero in V8 in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to perform a…
-
Unscored —
Inappropriate memory management when caching in PDFium in Google Chrome prior to 72.0.3626.81 allowed a remote attacker…
-
Unscored —
An incorrect object type assumption in SVG in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to potentia…
-
Unscored —
Incorrect object lifecycle management in Blink in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to pote…
-
Unscored —
Incorrect lifetime handling in HTML select elements in Google Chrome on Android and Mac prior to 72.0.3626.81 allowed a…
-
Unscored —
Insufficient checks of pointer validity in WebRTC in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to p…
-
Unscored —
Incorrect object lifecycle management in SwiftShader in Google Chrome prior to 72.0.3626.81 allowed a remote attacker t…
-
Unscored —
Inappropriate memory management when caching in PDFium in Google Chrome prior to 72.0.3626.81 allowed a remote attacker…
-
Unscored —
Failure to check error conditions in V8 in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to potentially…
-
Unscored —
Incorrect pointer management in WebRTC in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to potentially …
-
Unscored —
An exposed debugging endpoint in the browser in Google Chrome on Android prior to 72.0.3626.81 allowed a local attacker…
-
Unscored —
Incorrect handling of origin taint checking in Canvas in Google Chrome prior to 72.0.3626.81 allowed a remote attacker …
-
Unscored —
Insufficient protection of permission UI in WebAPKs in Google Chrome on Android prior to 72.0.3626.81 allowed an attack…
-
Unscored —
DevTools API not correctly gating on extension capability in DevTools in Google Chrome prior to 72.0.3626.81 allowed an…
-
Unscored —
Incorrect handling of invalid end character position when front rendering in Blink in Google Chrome prior to 72.0.3626.…
-
Unscored —
Insufficient input validation in WebGL in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to perform an o…
-
Unscored —
An incorrect JIT of GLSL shaders in SwiftShader in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to exe…
-
Unscored —
Sharing of objects over calls into JavaScript runtime in PDFium in Google Chrome prior to 72.0.3626.81 allowed a remote…
-
Unscored —
Insufficient origin validation in IndexedDB in Google Chrome prior to 72.0.3626.81 allowed a remote attacker who had co…
-
Unscored —
Omission of the .desktop filetype from the Safe Browsing checklist in SafeBrowsing in Google Chrome on Linux prior to 7…
-
Unscored —
Incorrect handling of a confusable character in Omnibox in Google Chrome prior to 72.0.3626.81 allowed a remote attacke…
-
Unscored —
Incorrect handling of a confusable character in Omnibox in Google Chrome prior to 72.0.3626.81 allowed a remote attacke…
-
Unscored —
Incorrect handling of a confusable character in Omnibox in Google Chrome prior to 72.0.3626.81 allowed a remote attacke…
-
Unscored —
A missing case for handling special schemes in permission request checks in Extensions in Google Chrome prior to 72.0.3…
-
Unscored —
Insufficient policy validation in ServiceWorker in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to byp…
-
Unscored —
Insufficient restrictions on what can be done with Apple Events in Google Chrome on macOS prior to 72.0.3626.81 allowed…
-
Unscored —
Incorrect handling of a confusable character in Omnibox in Google Chrome prior to 72.0.3626.81 allowed a remote attacke…
-
Unscored —
Incorrect optimization assumptions in V8 in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to execute ar…
-
Unscored —CVE-2019-5784 Public exploit
Incorrect handling of deferred code in V8 in Google Chrome prior to 72.0.3626.96 allowed a remote attacker to potential…
References
-
report
https://bugzilla.suse.com/1123641
-
report
https://bugzilla.suse.com/1124936
-
web
https://www.suse.com/security/cve/CVE-2019-5754
-
web
https://www.suse.com/security/cve/CVE-2019-5755
-
web
https://www.suse.com/security/cve/CVE-2019-5756
-
web
https://www.suse.com/security/cve/CVE-2019-5757
-
web
https://www.suse.com/security/cve/CVE-2019-5758
-
web
https://www.suse.com/security/cve/CVE-2019-5759
-
web
https://www.suse.com/security/cve/CVE-2019-5760
-
web
https://www.suse.com/security/cve/CVE-2019-5761
-
web
https://www.suse.com/security/cve/CVE-2019-5762
-
web
https://www.suse.com/security/cve/CVE-2019-5763
-
web
https://www.suse.com/security/cve/CVE-2019-5764
-
web
https://www.suse.com/security/cve/CVE-2019-5765
-
web
https://www.suse.com/security/cve/CVE-2019-5766
-
web
https://www.suse.com/security/cve/CVE-2019-5767
-
web
https://www.suse.com/security/cve/CVE-2019-5768
-
web
https://www.suse.com/security/cve/CVE-2019-5769
-
web
https://www.suse.com/security/cve/CVE-2019-5770
-
web
https://www.suse.com/security/cve/CVE-2019-5771
-
web
https://www.suse.com/security/cve/CVE-2019-5772
-
web
https://www.suse.com/security/cve/CVE-2019-5773
-
web
https://www.suse.com/security/cve/CVE-2019-5774
-
web
https://www.suse.com/security/cve/CVE-2019-5775
-
web
https://www.suse.com/security/cve/CVE-2019-5776
-
web
https://www.suse.com/security/cve/CVE-2019-5777
-
web
https://www.suse.com/security/cve/CVE-2019-5778
-
web
https://www.suse.com/security/cve/CVE-2019-5779
-
web
https://www.suse.com/security/cve/CVE-2019-5780
-
web
https://www.suse.com/security/cve/CVE-2019-5781
-
web
https://www.suse.com/security/cve/CVE-2019-5782
-
web
https://www.suse.com/security/cve/CVE-2019-5784