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

                               CERT-Renater

                   Note d'Information No. 2016/VULN387
_____________________________________________________________________

DATE                : 14/11/2016

HARDWARE PLATFORM(S): /

OPERATING SYSTEM(S): Systems running Google Chrome versions prior to
                         54.0.2840.99, 54.0.2840.98, 54.0.2840.100.

=====================================================================
https://googlechromereleases.blogspot.fr/2016/11/stable-channel-update-for-desktop_9.html
____________________________________________________________________


Stable Channel Update for Desktop

Wednesday, November 9, 2016

The stable channel has been updated to 54.0.2840.99 for Windows,
54.0.2840.98 for Mac, and 54.0.2840.100 on Linux. This will roll out
over the coming days/weeks.


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

[$5500][643948] High CVE-2016-5199: Heap corruption in FFmpeg.
                  Credit to Paul Mehta
[$5000][658114] High CVE-2016-5200: Out of bounds memory access in V8.
                  Credit to Choongwoo Han
[$1000][660678] Medium CVE-2016-5201: Info leak in extensions.
                  Credit to Rob Wu

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:

      [662843] CVE-2016-5202: Various fixes from internal audits, fuzzing
and other initiatives


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



A list of 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.



Richard Bustamante
Google Chrome

==========================================================
Serveur de référence du CERT-Renater
https://services.renater.fr/ssi/
==========================================================
+ 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 +
==========================================================