Summary
This update for chromium fixes the following issues:
Chromium 96.0.4664.110 (boo#1193713):
* CVE-2021-4098: Insufficient data validation in Mojo
* CVE-2021-4099: Use after free in Swiftshader
* CVE-2021-4100: Object lifecycle issue in ANGLE
* CVE-2021-4101: Heap buffer overflow in Swiftshader
* CVE-2021-4102: Use after free in V8
Lord of the Browsers: The Two Compilers:
* Go back to GCC
* GCC: LTO removes needed assembly symbols
* Clang: issues with libstdc++
Chromium 96.0.4664.93 (boo#1193519):
* CVE-2021-4052: Use after free in web apps
* CVE-2021-4053: Use after free in UI
* CVE-2021-4079: Out of bounds write in WebRTC
* CVE-2021-4054: Incorrect security UI in autofill
* CVE-2021-4078: Type confusion in V8
* CVE-2021-4055: Heap buffer overflow in extensions
* CVE-2021-4056: Type Confusion in loader
* CVE-2021-4057: Use after free in file API
* CVE-2021-4058: Heap buffer overflow in ANGLE
* CVE-2021-4059: Insufficient data validation in loader
* CVE-2021-4061: Type Confusion in V8
* CVE-2021-4062: Heap buffer overflow in BFCache
* CVE-2021-4063: Use after free in developer tools
* CVE-2021-4064: Use after free in screen capture
* CVE-2021-4065: Use after free in autofill
* CVE-2021-4066: Integer underflow in ANGLE
* CVE-2021-4067: Use after free in window manager
* CVE-2021-4068: Insufficient validation of untrusted input in new tab page
Chromium 96.0.4664.45 (boo#1192734):
* CVE-2021-38007: Type Confusion in V8
* CVE-2021-38008: Use after free in media
* CVE-2021-38009: Inappropriate implementation in cache
* CVE-2021-38006: Use after free in storage foundation
* CVE-2021-38005: Use after free in loader
* CVE-2021-38010: Inappropriate implementation in service workers
* CVE-2021-38011: Use after free in storage foundation
* CVE-2021-38012: Type Confusion in V8
* CVE-2021-38013: Heap buffer overflow in fingerprint recognition
* CVE-2021-38014: Out of bounds write in Swiftshader
* CVE-2021-38015: Inappropriate implementation in input
* CVE-2021-38016: Insufficient policy enforcement in background fetch
* CVE-2021-38017: Insufficient policy enforcement in iframe sandbox
* CVE-2021-38018: Inappropriate implementation in navigation
* CVE-2021-38019: Insufficient policy enforcement in CORS
* CVE-2021-38020: Insufficient policy enforcement in contacts picker
* CVE-2021-38021: Inappropriate implementation in referrer
* CVE-2021-38022: Inappropriate implementation in WebAuthentication
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| openSUSE · Leap 15.2 | chromium | 96.0.4664.110-lp152.2.143.1 |
Vulnerabilities 41
-
High 8.8CVE-2021-4102 Exploited
Use after free in V8 in Google Chrome prior to 96.0.4664.110 allowed a remote attacker to potentially exploit heap corr…
KEV Dec 15, 2021 -
Unscored —
Use after free in loader in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to potentially exploit heap c…
-
Unscored —
Use after free in storage foundation in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to potentially ex…
-
Unscored —
Type confusion in V8 in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to potentially exploit heap corru…
-
Unscored —
Use after free in media in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to potentially exploit heap co…
-
Unscored —
Inappropriate implementation in cache in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to leak cross-or…
-
Unscored —
Inappropriate implementation in service workers in Google Chrome prior to 96.0.4664.45 allowed a remote attacker who ha…
-
Unscored —
Use after free in storage foundation in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to potentially ex…
-
Unscored —
Type confusion in V8 in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to potentially exploit heap corru…
-
Unscored —
Heap buffer overflow in fingerprint recognition in Google Chrome on ChromeOS prior to 96.0.4664.45 allowed a remote att…
-
Unscored —
Out of bounds write in Swiftshader in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to potentially expl…
-
Unscored —
Inappropriate implementation in input in Google Chrome prior to 96.0.4664.45 allowed an attacker who convinced a user t…
-
Unscored —
Insufficient policy enforcement in background fetch in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to…
-
Unscored —
Insufficient policy enforcement in iframe sandbox in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to b…
-
Unscored —
Inappropriate implementation in navigation in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to perform …
-
Unscored —
Insufficient policy enforcement in CORS in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to leak cross-…
-
Unscored —
Insufficient policy enforcement in contacts picker in Google Chrome on Android prior to 96.0.4664.45 allowed a remote a…
-
Unscored —
Inappropriate implementation in referrer in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to bypass nav…
-
Unscored —
Inappropriate implementation in WebAuthentication in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to l…
-
Unscored —
Use after free in web apps in Google Chrome prior to 96.0.4664.93 allowed an attacker who convinced a user to install a…
-
Unscored —
Use after free in UI in Google Chrome on Linux prior to 96.0.4664.93 allowed a remote attacker to potentially exploit h…
-
Unscored —
Incorrect security UI in autofill in Google Chrome prior to 96.0.4664.93 allowed a remote attacker to perform domain sp…
-
Unscored —
Heap buffer overflow in extensions in Google Chrome prior to 96.0.4664.93 allowed an attacker who convinced a user to i…
-
Unscored —
Type confusion in loader in Google Chrome prior to 96.0.4664.93 allowed a remote attacker to potentially exploit heap c…
-
Unscored —
Use after free in file API in Google Chrome prior to 96.0.4664.93 allowed a remote attacker who had compromised the ren…
-
Unscored —
Heap buffer overflow in ANGLE in Google Chrome prior to 96.0.4664.93 allowed a remote attacker to potentially exploit h…
-
Unscored —
Insufficient data validation in loader in Google Chrome prior to 96.0.4664.93 allowed a remote attacker to leak cross-o…
-
Unscored —
Type confusion in V8 in Google Chrome prior to 96.0.4664.93 allowed a remote attacker to potentially exploit heap corru…
-
Unscored —
Heap buffer overflow in BFCache in Google Chrome prior to 96.0.4664.93 allowed a remote attacker who had compromised th…
-
Unscored —
Use after free in developer tools in Google Chrome prior to 96.0.4664.93 allowed a remote attacker to potentially explo…
-
Unscored —
Use after free in screen capture in Google Chrome on ChromeOS prior to 96.0.4664.93 allowed a remote attacker to potent…
-
Unscored —
Use after free in autofill in Google Chrome prior to 96.0.4664.93 allowed a remote attacker to potentially exploit heap…
-
Unscored —
Integer underflow in ANGLE in Google Chrome prior to 96.0.4664.93 allowed a remote attacker to potentially exploit heap…
-
Unscored —
Use after free in window manager in Google Chrome on ChromeOS prior to 96.0.4664.93 allowed a remote attacker to potent…
-
Unscored —
Insufficient data validation in new tab page in Google Chrome prior to 96.0.4664.93 allowed a remote attacker to leak c…
-
Unscored —
Type confusion in V8 in Google Chrome prior to 96.0.4664.93 allowed a remote attacker to potentially exploit heap corru…
-
Unscored —
Out of bounds write in WebRTC in Google Chrome prior to 96.0.4664.93 allowed a remote attacker to potentially exploit h…
-
Unscored —
Insufficient data validation in Mojo in Google Chrome prior to 96.0.4664.110 allowed a remote attacker who had compromi…
-
Unscored —
Use after free in Swiftshader in Google Chrome prior to 96.0.4664.110 allowed a remote attacker to potentially exploit …
-
Unscored —
Object lifecycle issue in ANGLE in Google Chrome prior to 96.0.4664.110 allowed a remote attacker to potentially exploi…
-
Unscored —
Heap buffer overflow in Swiftshader in Google Chrome prior to 96.0.4664.110 allowed a remote attacker to potentially ex…
References
-
report
https://bugzilla.suse.com/1192310
-
report
https://bugzilla.suse.com/1192734
-
report
https://bugzilla.suse.com/1193519
-
report
https://bugzilla.suse.com/1193713
-
web
https://www.suse.com/security/cve/CVE-2021-38005
-
web
https://www.suse.com/security/cve/CVE-2021-38006
-
web
https://www.suse.com/security/cve/CVE-2021-38007
-
web
https://www.suse.com/security/cve/CVE-2021-38008
-
web
https://www.suse.com/security/cve/CVE-2021-38009
-
web
https://www.suse.com/security/cve/CVE-2021-38010
-
web
https://www.suse.com/security/cve/CVE-2021-38011
-
web
https://www.suse.com/security/cve/CVE-2021-38012
-
web
https://www.suse.com/security/cve/CVE-2021-38013
-
web
https://www.suse.com/security/cve/CVE-2021-38014
-
web
https://www.suse.com/security/cve/CVE-2021-38015
-
web
https://www.suse.com/security/cve/CVE-2021-38016
-
web
https://www.suse.com/security/cve/CVE-2021-38017
-
web
https://www.suse.com/security/cve/CVE-2021-38018
-
web
https://www.suse.com/security/cve/CVE-2021-38019
-
web
https://www.suse.com/security/cve/CVE-2021-38020
-
web
https://www.suse.com/security/cve/CVE-2021-38021
-
web
https://www.suse.com/security/cve/CVE-2021-38022
-
web
https://www.suse.com/security/cve/CVE-2021-4052
-
web
https://www.suse.com/security/cve/CVE-2021-4053
-
web
https://www.suse.com/security/cve/CVE-2021-4054
-
web
https://www.suse.com/security/cve/CVE-2021-4055
-
web
https://www.suse.com/security/cve/CVE-2021-4056
-
web
https://www.suse.com/security/cve/CVE-2021-4057
-
web
https://www.suse.com/security/cve/CVE-2021-4058
-
web
https://www.suse.com/security/cve/CVE-2021-4059
-
web
https://www.suse.com/security/cve/CVE-2021-4061
-
web
https://www.suse.com/security/cve/CVE-2021-4062
-
web
https://www.suse.com/security/cve/CVE-2021-4063
-
web
https://www.suse.com/security/cve/CVE-2021-4064
-
web
https://www.suse.com/security/cve/CVE-2021-4065
-
web
https://www.suse.com/security/cve/CVE-2021-4066
-
web
https://www.suse.com/security/cve/CVE-2021-4067
-
web
https://www.suse.com/security/cve/CVE-2021-4068
-
web
https://www.suse.com/security/cve/CVE-2021-4078