Bug 30961 - chromium stable updated to 106.0.5249.119 to bring security updates
Summary: chromium stable updated to 106.0.5249.119 to bring security updates
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Security (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact: Sec team
URL:
Whiteboard: MGA8-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2022-10-13 12:59 CEST by christian barranco
Modified: 2022-10-19 01:16 CEST (History)
7 users (show)

See Also:
Source RPM: chromium-browser-stable-106.0.5249.91-1.mga8.src.rpm
CVE:
Status comment:


Attachments

Description christian barranco 2022-10-13 12:59:33 CEST
Hi
New security update:
https://chromereleases.googleblog.com/2022/10/stable-channel-update-for-desktop_11.html
Comment 1 christian barranco 2022-10-14 14:47:04 CEST
ADVISORY NOTICE PROPOSAL
========================

New chromium-browser-stable update fixes bugs and vulnerabilities


Description
The chromium-browser-stable package has been updated to the new 106 branch with the 106.0.5249.119 version, fixing many bugs and 6 vulnerabilities.
Some of the security fixes are:

High CVE-2022-3445: Use after free in Skia. Reported by Nan Wang (@eternalsakura13) and Yong Liu of 360 Vulnerability Research Institute on 2022-09-16
High CVE-2022-3446: Heap buffer overflow in WebSQL. Reported by Kaijie Xu (@kaijieguigui) on 2022-09-26
High CVE-2022-3447: Inappropriate implementation in Custom Tabs. Reported by Narendra Bhati of Suma Soft Pvt. Ltd. Pune (India) on 2022-09-22
High CVE-2022-3448: Use after free in Permissions API. Reported by raven at KunLun lab on 2022-09-13
High CVE-2022-3449: Use after free in Safe Browsing. Reported by asnine on 2022-09-17
High CVE-2022-3450: Use after free in Peer Connection. Reported by Anonymous on 2022-09-30


References
https://bugs.mageia.org/show_bug.cgi?id=30961
https://chromereleases.googleblog.com/2022/10/stable-channel-update-for-desktop_11.html
https://blog.chromium.org/2022/09/chrome-106-beta-new-css-features.html



SRPMS
8/core
chromium-browser-stable-106.0.5249.119-1.mga8


PROVIDED PACKAGES
=================
x86_64
chromium-browser-106.0.5249.119-1.mga8.x86_64.rpm
chromium-browser-stable-106.0.5249.119-1.mga8.x86_64.rpm

i586
chromium-browser-106.0.5249.119-1.mga8.i586.rpm
chromium-browser-stable-106.0.5249.119-1.mga8.i586.rpm
Comment 2 christian barranco 2022-10-14 17:05:45 CEST
Ready for QA

Assignee: chb0 => qa-bugs
CC: (none) => sysadmin-bugs

David Walser 2022-10-14 18:43:55 CEST

CC: sysadmin-bugs => (none)

Comment 3 Brian Rockwell 2022-10-14 19:57:44 CEST
MGA8-64, Gnome

Installed x86_64 packages no issues


- Jitsi Meet - working
- youtube - working
- various websites - working

works for me

CC: (none) => brtians1

Comment 4 Herman Viaene 2022-10-15 10:53:02 CEST
MGA8-64 MATE on Acer Aspire 5253
No installation  issues.
Tested with newspapersite, Google Maps and Youtube, all OK.

CC: (none) => herman.viaene

Comment 5 Morgan Leijström 2022-10-17 08:47:27 CEST
mga8-64, plasma, nvidia-current, i7

OK:
Swedish localisation
Restored tabs, kept settings
Tried three different login methods (2 Qr phone apps, one F2A)
A few more sites incl video

CC: (none) => fri

Comment 6 Guillaume Royer 2022-10-17 12:01:57 CEST
mga8 64 XFCE core I3 6Go RAM

No installations issues, tested with:

- Bank site
- Streaming Websites like Netflix
- Element browser client for Matrix
- Facebook

Ok for me

CC: (none) => guillaume.royer

Brian Rockwell 2022-10-17 14:17:54 CEST

Whiteboard: (none) => MGA8-64-OK

Comment 7 Thomas Andrews 2022-10-18 01:41:18 CEST
Validating. Advisory in Comment 1.

Keywords: (none) => validated_update
CC: (none) => andrewsfarm, sysadmin-bugs

Dave Hodgins 2022-10-18 23:16:18 CEST

Keywords: (none) => advisory
CC: (none) => davidwhodgins

Comment 8 Mageia Robot 2022-10-19 01:16:30 CEST
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGASA-2022-0376.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.