====================================================================

                             CERT-Renater

                 Note d'Information No. 2020/VULN090
_____________________________________________________________________

DATE                : 25/02/2020

HARDWARE PLATFORM(S): /

OPERATING SYSTEM(S): Systems running Google Chrome versions prior to
                                      80.0.3987.122.

=====================================================================
https://chromereleases.googleblog.com/2020/02/stable-channel-update-for-desktop_24.html
_____________________________________________________________________

Stable Channel Update for Desktop
Monday, February 24, 2020

The stable channel has been updated to 80.0.3987.122 for Windows, Mac,
and Linux, which will roll out over the coming days/weeks.


A list of all changes is available in the log. Interested in switching
release channels?  Find out how. 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.


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 3 security fixes. Below, we highlight fixes that
were contributed by external researchers. Please see the Chrome Security
Page for more information.


[$5000][1044570] High: Integer overflow in ICU. Reported by André
Bargull on 2020-01-22

[N/A][1045931] High CVE-2020-6407: Out of bounds memory access in
streams. Reported by Sergei Glazunov of Google Project Zero on
2020-01-27


This release also contains:
[N/A][1053604] High CVE-2020-6418: Type confusion in V8. Reported by
Clement Lecigne of Google's Threat Analysis Group on 2020-02-18


Google is aware of reports that an exploit for CVE-2020-6418 exists in
the wild.


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.


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




Krishna Govind
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   +
=========================================================