===================================================================                             CERT-Renater

                  Note d'Information No. 2023/VULN145

_____________________________________________________________________

DATE                : 05/04/2023

HARDWARE PLATFORM(S): /

OPERATING SYSTEM(S): Systems running Google Chrome versions prior to
                                      112.0.5615.49/50.

====================================================================https://chromereleases.googleblog.com/2023/04/stable-channel-update-for-desktop.html
_____________________________________________________________________


Stable Channel Update for Desktop
Tuesday, April 4, 2023


The Chrome team is delighted to announce the promotion of Chrome 112
to the stable channel for Windows, Mac and Linux. This will roll out
over the coming days/weeks.



Chrome 112.0.5615.49 (Linux and Mac), 112.0.5615.49/50( Windows)
contains a number of fixes and improvements -- a list of changes
is available in the log. Watch out for upcoming Chrome and Chromium
blog posts about new features and big efforts delivered in 112.


Security Fixes and Rewards

Note: Access to bug details and links may be kept restricted
until a majority of users are updated with a fix. We will also
retain restrictions if the bug exists in a third party library
that other projects similarly depend on, but haven’t yet fixed.


This update includes 16 security fixes. Below, we highlight fixes
that were contributed by external researchers. Please see the
Chrome Security Page for more information.


[$5000][1414018] High CVE-2023-1810: Heap buffer overflow in Visuals.
Reported by Weipeng Jiang (@Krace) of VRI on 2023-02-08

[$3000][1420510] High CVE-2023-1811: Use after free in Frames.
Reported by Thomas Orlita on 2023-03-01

[$5000][1418224] Medium CVE-2023-1812: Out of bounds memory access
in DOM Bindings. Reported by Shijiang Yu on 2023-02-22

[$5000][1423258] Medium CVE-2023-1813: Inappropriate implementation
in Extensions. Reported by Axel Chong on 2023-03-10

[$3000][1417325] Medium CVE-2023-1814: Insufficient validation of
untrusted input in Safe Browsing. Reported by Young Min Kim
(@ylemkimon), CompSec Lab at Seoul National University on 2023-02-18

[$2000][1278708] Medium CVE-2023-1815: Use after free in Networking
APIs. Reported by DDV_UA on 2021-12-10

[$1000][1413919] Medium CVE-2023-1816: Incorrect security UI in
Picture In Picture. Reported by NDevTK on 2023-02-08

[$1000][1418061] Medium CVE-2023-1817: Insufficient policy
enforcement in Intents. Reported by Axel Chong on 2023-02-22

[$NA][1223346] Medium CVE-2023-1818: Use after free in Vulkan.
Reported by Abdulrahman Alqabandi, Microsoft Browser Vulnerability
Research, Eric Lawrence, Microsoft, Patrick Walker (@HomeSen),
and Kirtikumar Anandrao Ramchandani on 2021-06-24

[$NA][1406588] Medium CVE-2023-1819: Out of bounds read in
Accessibility. Reported by Microsoft Edge Team on 2023-01-12

[$TBD][1408120] Medium CVE-2023-1820: Heap buffer overflow in
Browser History. Reported by raven at KunLun lab on 2023-01-17

[$1000][1413618] Low CVE-2023-1821: Inappropriate implementation
in WebShare. Reported by Axel Chong on 2023-02-07

[$500][1066555] Low CVE-2023-1822: Incorrect security UI in
Navigation. Reported by 강우진 on 2020-04-01

[$TBD][1406900] Low CVE-2023-1823: Inappropriate implementation
in FedCM. Reported by Jasper Rebane (popstonia) on 2023-01-13




We would also like to thank all security researchers that worked
with us during the development cycle to prevent security bugs
from ever reaching the stable channel.

As usual, our ongoing internal security work was responsible
for a wide range of fixes:

[1430254] Various fixes from internal audits, fuzzing and
other initiatives


Many of our security bugs are detected using AddressSanitizer,
MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow
Integrity, libFuzzer, or AFL.


Interested in switching release channels? Find out how here. If
you find a new issue, please let us know by filing a bug. The
community help forum is also a great place to reach out for
help or learn about common issues.


Srinivas Sista
Google Chrome


========================================================+ CERT-RENATER        |    tel : 01-53-94-20-44         +
+ 23/25 Rue Daviel    |    fax : 01-53-94-20-41         +
+ 75013 Paris         |   email:cert@support.renater.fr +
=======================================================