Summary
This update for chromium fixes the following issues:
Chromium was updated to 83.0.4103.97 (boo#1171910,bsc#1172496):
* CVE-2020-6463: Use after free in ANGLE (boo#1170107 boo#1171975).
* CVE-2020-6465: Use after free in reader mode. Reported by Woojin Oh(@pwn_expoit) of STEALIEN on 2020-04-21
* CVE-2020-6466: Use after free in media. Reported by Zhe Jin from cdsrc of Qihoo 360 on 2020-04-26
* CVE-2020-6467: Use after free in WebRTC. Reported by ZhanJia Song on 2020-04-06
* CVE-2020-6468: Type Confusion in V8. Reported by Chris Salls and Jake Corina of Seaside Security, Chani Jindal of Shellphish on 2020-04-30
* CVE-2020-6469: Insufficient policy enforcement in developer tools. Reported by David Erceg on 2020-04-02
* CVE-2020-6470: Insufficient validation of untrusted input in clipboard. Reported by Michał Bentkowski of Securitum on 2020-03-30
* CVE-2020-6471: Insufficient policy enforcement in developer tools. Reported by David Erceg on 2020-03-08
* CVE-2020-6472: Insufficient policy enforcement in developer tools. Reported by David Erceg on 2020-03-25
* CVE-2020-6473: Insufficient policy enforcement in Blink. Reported by Soroush Karami and Panagiotis Ilia on 2020-02-06
* CVE-2020-6474: Use after free in Blink. Reported by Zhe Jin from cdsrc of Qihoo 360 on 2020-03-07
* CVE-2020-6475: Incorrect security UI in full screen. Reported by Khalil Zhani on 2019-10-31
* CVE-2020-6476: Insufficient policy enforcement in tab strip. Reported by Alexandre Le Borgne on 2019-12-18
* CVE-2020-6477: Inappropriate implementation in installer. Reported by RACK911 Labs on 2019-03-26
* CVE-2020-6478: Inappropriate implementation in full screen. Reported by Khalil Zhani on 2019-12-24
* CVE-2020-6479: Inappropriate implementation in sharing. Reported by Zhong Zhaochen of andsecurity.cn on 2020-01-14
* CVE-2020-6480: Insufficient policy enforcement in enterprise. Reported by Marvin Witt on 2020-02-21
* CVE-2020-6481: Insufficient policy enforcement in URL formatting. Reported by Rayyan Bijoora on 2020-04-07
* CVE-2020-6482: Insufficient policy enforcement in developer tools. Reported by Abdulrahman Alqabandi (@qab) on 2017-12-17
* CVE-2020-6483: Insufficient policy enforcement in payments. Reported by Jun Kokatsu, Microsoft Browser Vulnerability Research on 2019-05-23
* CVE-2020-6484: Insufficient data validation in ChromeDriver. Reported by Artem Zinenko on 2020-01-26
* CVE-2020-6485: Insufficient data validation in media router. Reported by Sergei Glazunov of Google Project Zero on 2020-01-30
* CVE-2020-6486: Insufficient policy enforcement in navigations. Reported by David Erceg on 2020-02-24
* CVE-2020-6487: Insufficient policy enforcement in downloads. Reported by Jun Kokatsu (@shhnjk) on 2015-10-06
* CVE-2020-6488: Insufficient policy enforcement in downloads. Reported by David Erceg on 2020-01-21
* CVE-2020-6489: Inappropriate implementation in developer tools. Reported by @lovasoa (Ophir LOJKINE) on 2020-02-10
* CVE-2020-6490: Insufficient data validation in loader. Reported by Twitter on 2019-12-19
* CVE-2020-6491: Incorrect security UI in site information. Reported by Sultan Haikal M.A on 2020-02-07
* CVE-2020-6493: Use after free in WebAuthentication.
* CVE-2020-6494: Incorrect security UI in payments.
* CVE-2020-6495: Insufficient policy enforcement in developer tools.
* CVE-2020-6496: Use after free in payments.
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| openSUSE · Leap 15.1 | chromium | 83.0.4103.97-lp151.2.96.1 |
Vulnerabilities 32
-
Unscored —
Use after free in ANGLE in Google Chrome prior to 81.0.4044.122 allowed a remote attacker to potentially exploit heap c…
-
Unscored —
Use after free in reader mode in Google Chrome on Android prior to 83.0.4103.61 allowed a remote attacker who had compr…
-
Unscored —
Use after free in media in Google Chrome prior to 83.0.4103.61 allowed a remote attacker who had compromised the render…
-
Unscored —
Use after free in WebRTC in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to potentially exploit heap c…
-
Unscored —CVE-2020-6468 Public exploit
Type confusion in V8 in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to potentially exploit heap corru…
-
Unscored —
Insufficient policy enforcement in developer tools in Google Chrome prior to 83.0.4103.61 allowed an attacker who convi…
-
Unscored —
Insufficient validation of untrusted input in clipboard in Google Chrome prior to 83.0.4103.61 allowed a local attacker…
-
Unscored —
Insufficient policy enforcement in developer tools in Google Chrome prior to 83.0.4103.61 allowed an attacker who convi…
-
Unscored —
Insufficient policy enforcement in developer tools in Google Chrome prior to 83.0.4103.61 allowed an attacker who convi…
-
Unscored —
Insufficient policy enforcement in Blink in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to obtain pot…
-
Unscored —
Use after free in Blink in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to potentially exploit heap co…
-
Unscored —
Incorrect implementation in full screen in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to spoof secur…
-
Unscored —
Insufficient policy enforcement in tab strip in Google Chrome prior to 83.0.4103.61 allowed an attacker who convinced a…
-
Unscored —
Inappropriate implementation in installer in Google Chrome on OS X prior to 83.0.4103.61 allowed a local attacker to pe…
-
Unscored —
Inappropriate implementation in full screen in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to spoof s…
-
Unscored —
Inappropriate implementation in sharing in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to spoof secur…
-
Unscored —
Insufficient policy enforcement in enterprise in Google Chrome prior to 83.0.4103.61 allowed a local attacker to bypass…
-
Unscored —
Insufficient policy enforcement in URL formatting in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to p…
-
Unscored —
Insufficient policy enforcement in developer tools in Google Chrome prior to 83.0.4103.61 allowed an attacker who convi…
-
Unscored —
Insufficient policy enforcement in payments in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypass …
-
Unscored —
Insufficient data validation in ChromeDriver in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypass…
-
Unscored —
Insufficient data validation in media router in Google Chrome prior to 83.0.4103.61 allowed a remote attacker who had c…
-
Unscored —
Insufficient policy enforcement in navigations in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypa…
-
Unscored —
Insufficient policy enforcement in downloads in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypass…
-
Unscored —
Insufficient policy enforcement in downloads in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypass…
-
Unscored —
Inappropriate implementation in developer tools in Google Chrome prior to 83.0.4103.61 allowed a remote attacker who ha…
-
Unscored —
Insufficient data validation in loader in Google Chrome prior to 83.0.4103.61 allowed a remote attacker who had been ab…
-
Unscored —
Insufficient data validation in site information in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to sp…
-
Unscored —
Use after free in WebAuthentication in Google Chrome prior to 83.0.4103.97 allowed a remote attacker who had compromise…
-
Unscored —
Incorrect security UI in payments in Google Chrome on Android prior to 83.0.4103.97 allowed a remote attacker to spoof …
-
Unscored —
Insufficient policy enforcement in developer tools in Google Chrome prior to 83.0.4103.97 allowed an attacker who convi…
-
Unscored —
Use after free in payments in Google Chrome on MacOS prior to 83.0.4103.97 allowed a remote attacker to potentially per…
References
-
report
https://bugzilla.suse.com/1170107
-
report
https://bugzilla.suse.com/1171910
-
report
https://bugzilla.suse.com/1171975
-
report
https://bugzilla.suse.com/1172496
-
web
https://www.suse.com/security/cve/CVE-2020-6463
-
web
https://www.suse.com/security/cve/CVE-2020-6465
-
web
https://www.suse.com/security/cve/CVE-2020-6466
-
web
https://www.suse.com/security/cve/CVE-2020-6467
-
web
https://www.suse.com/security/cve/CVE-2020-6468
-
web
https://www.suse.com/security/cve/CVE-2020-6469
-
web
https://www.suse.com/security/cve/CVE-2020-6470
-
web
https://www.suse.com/security/cve/CVE-2020-6471
-
web
https://www.suse.com/security/cve/CVE-2020-6472
-
web
https://www.suse.com/security/cve/CVE-2020-6473
-
web
https://www.suse.com/security/cve/CVE-2020-6474
-
web
https://www.suse.com/security/cve/CVE-2020-6475
-
web
https://www.suse.com/security/cve/CVE-2020-6476
-
web
https://www.suse.com/security/cve/CVE-2020-6477
-
web
https://www.suse.com/security/cve/CVE-2020-6478
-
web
https://www.suse.com/security/cve/CVE-2020-6479
-
web
https://www.suse.com/security/cve/CVE-2020-6480
-
web
https://www.suse.com/security/cve/CVE-2020-6481
-
web
https://www.suse.com/security/cve/CVE-2020-6482
-
web
https://www.suse.com/security/cve/CVE-2020-6483
-
web
https://www.suse.com/security/cve/CVE-2020-6484
-
web
https://www.suse.com/security/cve/CVE-2020-6485
-
web
https://www.suse.com/security/cve/CVE-2020-6486
-
web
https://www.suse.com/security/cve/CVE-2020-6487
-
web
https://www.suse.com/security/cve/CVE-2020-6488
-
web
https://www.suse.com/security/cve/CVE-2020-6489
-
web
https://www.suse.com/security/cve/CVE-2020-6490
-
web
https://www.suse.com/security/cve/CVE-2020-6491
-
web
https://www.suse.com/security/cve/CVE-2020-6493
-
web
https://www.suse.com/security/cve/CVE-2020-6494
-
web
https://www.suse.com/security/cve/CVE-2020-6495
-
web
https://www.suse.com/security/cve/CVE-2020-6496